 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| april 2011 208045-11 1 numonyx? axcell? m29ew datasheet 256-mbit, 512-mbit, 1-gbit, 2- gbit (x8/x16, uniform block) 3 v supply flash memory features ? supply voltage ?v cc = 2.7 to 3.6 v for program, erase and read ?v ccq = 1.65 to 3.6 v for i/o buffers ? asynchronous random/page read ? page size: 16 words or 32 bytes ? page access: 25 ns ? random access: 100ns (fortified bga); 110 ns (tsop) ? buffer program ? 512-word program buffer ? programming time ? 0.88 s per byte (1.14mb/s) typical when using full buffer size in buffer program ? memory organization ? uniform blocks, 128 kbytes/64 kwords each ? program/erase controller ? embedded byte/word program algorithms ? program/ erase suspend and resume ? read from any block during program suspend ? read and program another block during erase suspend ? blank check to verify an erased block ? unlock bypass/block erase/chip erase/write to buffer ? faster buffered/batch programming ? faster block and chip erase ? vpp/wp# pin protection ? protects first or last block regardless of block protection settings ? software protection ? volatile protection ? non-volatile protection ? password protection ? password access ? extended memory block ? 128-word/256-byte block for permanent, secure identification. ? can be programmed and locked by factory or by the customer ? low power consumption ? standby ? minimum 100,000 program/erase cycles per block ? etox tm * x (65nm) mlc technology ? fortified bga and tsop packages ? jesd47e compliant ? green packages available ?rohs compliant ? halogen free http://www..net/ datasheet pdf - http://www..net/
table of contents numonyx? axcell? m29ew 2 208045-11 1 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2 signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.1 address inputs (a0-amax) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.2 data inputs/outputs (dq0-dq7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3 data inputs/outputs (dq8-dq14) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.4 data input/output or address input (dq15/a-1) . . . . . . . . . . . . . . . . . . . . 13 2.5 chip enable (ce#) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.6 output enable (oe#) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.7 write enable (we#) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.8 v pp /write protect (v pp/ wp#) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.9 reset (rst#) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.10 ready/busy output (ry/by#) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.11 byte/word organization select (byte#) . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.12 v cc supply voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.13 v ccq input/output supply voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.14 v ss ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3 bus operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.1 bus read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.2 bus write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.3 output disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.4 standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.5 reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.6 auto select mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.6.1 read electronic signature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.6.2 verify extended memory block protection indicator . . . . . . . . . . . . . . . . 18 3.6.3 verify block protection status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.6.4 hardware block protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 4 hardware protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5 software protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.1 volatile protection mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.2 non-volatile protection mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew table of contents 208045-11 3 5.2.1 non-volatile protection bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.2.2 non-volatile protection bit lock bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.3 password protection mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 6 command interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1 standard commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1.1 read/reset command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1.2 auto select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1.3 read cfi query command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.1.4 chip erase command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.1.5 block erase command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.1.6 blank check command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.1.7 erase suspend command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.1.8 erase resume command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.1.9 program suspend command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 6.1.10 program resume command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 6.1.11 program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 6.2 fast program commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.2.1 write to buffer program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.2.2 buffered program abort and reset command . . . . . . . . . . . . . . . . . . . . 38 6.2.3 write to buffer program confirm command . . . . . . . . . . . . . . . . . . . . . . 39 6.2.4 unlock bypass command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.2.5 unlock bypass program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.2.6 unlock bypass block erase command . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.2.7 unlock bypass chip erase command . . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.2.8 unlock bypass write to buffer program command . . . . . . . . . . . . . . . . 40 6.2.9 unlock bypass reset command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.3 protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 6.3.1 enter extended memory block command . . . . . . . . . . . . . . . . . . . . . . . 43 6.3.2 exit extended memory block command . . . . . . . . . . . . . . . . . . . . . . . . 43 6.3.3 lock register command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 6.3.4 password protection mode command set . . . . . . . . . . . . . . . . . . . . . . . 44 6.3.5 non-volatile protection mode command set . . . . . . . . . . . . . . . . . . . . . 45 6.3.6 nvpb lock bit command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 6.3.7 volatile protection mode command set . . . . . . . . . . . . . . . . . . . . . . . . . 47 6.3.8 exit protection command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 http://www..net/ datasheet pdf - http://www..net/ table of contents numonyx? axcell? m29ew 4 208045-11 7 registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 7.1 lock register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 7.1.1 password protection mode lock bit (dq2) . . . . . . . . . . . . . . . . . . . . . . 52 7.1.2 non-volatile protection mode lock bit (dq1) . . . . . . . . . . . . . . . . . . . . . 52 7.1.3 extended memory block protection bit (dq0) . . . . . . . . . . . . . . . . . . . . 52 7.2 status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 7.2.1 data polling bit (dq7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 7.2.2 toggle bit (dq6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 7.2.3 error bit (dq5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 7.2.4 erase timer bit (dq3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 7.2.5 alternative toggle bit (dq2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 7.2.6 buffered program abort bit (dq1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 8 maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 9 dc and ac parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 10 programming and erase performance . . . . . . . . . . . . . . . . . . . . . . . . . 77 11 package mechanical specificat ions . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 12 ordering information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 appendix a memory address ta ble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 appendix b common flash interface (c fi) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 appendix c extended memory block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 c.1 numonyx pre-locked extended memory block . . . . . . . . . . . . . . . . . . . . 116 c.2 customer-lockable extended memory block . . . . . . . . . . . . . . . . . . . . . . 117 appendix d revision history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew list of tables 208045-11 5 table 1. signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 table 2. v pp /wp# functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 table 3. bus operations, 8-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 4. bus operations, 16-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 5. read electronic signature - auto select mode - programmer method (8-bit mode) . . . . . . 21 table 6. read electronic signature - auto select mode - programmer method (16-bit mode) . . . . . 21 table 7. block protection - auto select mode - programmer method (8-bit mode) . . . . . . . . . . . . . . 22 table 8. block protection - auto select mode - programmer method (16-bit mode) . . . . . . . . . . . . . 22 table 9. standard commands, 8-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3 table 10. standard commands, 16-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4 table 11. fast program commands, 8-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 table 12. fast program commands, 16-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 table 13. block protection commands, 8-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 table 14. block protection commands, 16-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 table 15. lock register bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 16. block protection status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 17. status register bits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 table 18. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 table 19. operating and ac measurement conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 table 20. power-up wait timings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 table 21. device capacitance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 table 22. dc characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 table 23. read ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 table 24. write ac characteristics, write enable controlled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 table 25. write ac characteristics, chip enable controlled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 26. reset ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 table 27. accelerated program and data polling/data toggle ac characteristics . . . . . . . . . . . . . . 76 table 28. programming and erase performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 table 29. tsop56 ? 56 lead thin small-outline package, 14 x 20 mm, package mechanical data . . 78 table 30. fortified bga64 11 x 13 mm - 8 x 8 active ball array, package mechanical data. . . . . . . . 79 table 31. ordering information scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 table 32. valid combinations of m29ew part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 table 33. block address table for descrete device (up to 1-gbit) . . . . . . . . . . . . . . . . . . . . . . . . . . 81 table 34. query structure overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 table 35. cfi query identification string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 table 36. cfi query system interface information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 table 37. device geometry definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 table 38. primary algorithm-specific extended query table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 table 39. extended memory block address and data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 table 40. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 http://www..net/ datasheet pdf - http://www..net/ list of figures numonyx? axcell? m29ew 6 208045-11 figure 1. logic diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 2. 2-gbit (1-gbit/1-gbit stack) configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 3. tsop connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 4. fortified bga connections (top and bottom views). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 5. block addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 figure 6. software protection scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 figure 7. boundary condition of program buffer size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 figure 8. write to buffer program fletcher and pseudo code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 figure 9. nvpb program/erase algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 figure 10. lock register program flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 figure 11. data polling flow chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 figure 12. toggle flow chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 figure 13. status register polling flow chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 figure 14. ac measurement load circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 figure 15. ac measurement i/o waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 figure 16. power-up wait timings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 figure 17. random read ac waveforms (8-bit mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 figure 18. random read ac waveforms (16-bit mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 figure 19. byte# transition ac waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 figure 20. page read ac waveforms (16-bit mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 figure 21. write enable controlled program waveforms (8-bit mode) . . . . . . . . . . . . . . . . . . . . . . . . 67 figure 22. write enable controlled program waveforms (16-bit mode) . . . . . . . . . . . . . . . . . . . . . . . 69 figure 23. chip enable controlled program waveforms (8-bit mode) . . . . . . . . . . . . . . . . . . . . . . . . . 71 figure 24. chip enable controlled program waveforms (16-bit mode) . . . . . . . . . . . . . . . . . . . . . . . . 72 figure 25. chip/block erase waveforms (8-bit mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 figure 26. reset ac waveforms (no program/erase in progress) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 figure 27. reset during program/erase operation ac waveforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 figure 28. accelerated program timing waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 figure 29. data polling ac waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 figure 30. toggle/alternative toggle bit polling ac waveforms (8-bit mode) . . . . . . . . . . . . . . . . . . . 76 figure 31. tsop56 ? 56 lead thin small-outline package, 14 x 20 mm, package outline . . . . . . . . . . 78 figure 32. fortified bga64 11 x 13 mm - 8 x 8 active ball array, package outline . . . . . . . . . . . . . . . 79 http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew description 208045-11 7 1 description the numonyx? axcell? m29ew flash memory based on 65nm mlc technology is the world?s leading line of parallel nor flash for embedded applications. it can be read, erased and reprogrammed; and these operations can be performed using a single low voltage (2.7 to 3.6 v) supply. upon power-up, the memory defaults to its array read mode. the main memory array is divided into 64-kword/128-kbyte uniform blocks that can be erased independently so that valid data can be preserved while old data is purged. program and erase commands are written to the command interface of the memory. an on-chip program/erase controller simplifies the process of programming or erasing the memory by taking care of all of the special operations that are required to update the memory contents. the end of a program or erase operation can be detected and any error condition can be identified. the command set required to cont rol the memory is consistent with jedec standards. chip enable, output enable and write enable signals control the bus operation of the memory. they allow simple connection to most microprocessors, often without additional logic. the m29ew supports asynchronous random read and page read from all blocks of the memory array. it also features an internal program buffer which improves throughput by programming 512 words via one command sequence. the m29ew contains a 128-word extended memory block which overlaps addresses with array block 0. the user can program this additi onal space; then protect it to permanently secure its contents. the device features different levels of hardware and software protection to secure blocks from unwanted modification (program or erase): l hardware protection: ?the v pp /wp# provides a hardware protection of either the highest (m29ewh) or the lowest (m29ewl) block of the main memory array. l software protection: ? volatile protection ? non-volatile protection ? password protection ? password access the m29ew is offered in tsop56 (14 x 20 mm) and fortified bga64 (11 x 13 mm, 1 mm pitch) packages. the memories are delivered with all the bits erased (set to ?1?). also see appendix b: common flash interface (cfi) on page 112 and ta bl e 5 : b l o ck addresses on page 12 for a full list of the block addresses. http://www..net/ datasheet pdf - http://www..net/ description numonyx? axcell? m29ew 8 208045-11 figure 1. logic diagram 1. a23 is valid for 256-mbit densit y and above; otherwise, it is rfu. 2. a24 is valid for 512-mbit densit y and above; otherwise, it is rfu. 3. a25 is valid for 1-gbit density and above; otherwise, it is rfu. 4. a26 is valid for 2-gbit (1-gbit/1-gbit stack) density only; otherwise it?s rfu. 5. rfu stands for reserved for future use and should be not connect. table 1. signal descriptions name description direction a0-amax address inputs inputs dq0-dq7 data inputs/outputs i/o dq8-dq14 data inputs/outputs i/o dq15/a ? 1 data input/output or address input i/o ce# chip enable input oe# output enable input we# write enable input rst# reset input ry/by# ready/busy output output byte# byte/word organization select input v ccq input/output buffer supply voltage supply v cc supply voltage supply v pp /wp# (1) v pp /write protect input v ss ground - nc not connected - 1. v pp /wp# may be left unconnected as it is in ternally connected to a pull-up resistor , which enables program/erase operations. m29ew v cc v ccq a0 ? amax we# v pp /wp# dq0 ? dq14 dq15 / a-1 v ss 15 ce# oe # rst# byte# ry/by# http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew description 208045-11 9 figure 2. 2-gbit (1-gbit/1-gbit stack) configurations 1. a max = v ih selects the upper die; a max = v il selects the lower die. upper die (1-gbit) lower die (1-gbit) vpp/wp# ce# byte# oe# we# rst# vcc dq[14:0] a[26:0] vccq vss 2-gbit (1-gbit/1-gbit stack) configuration dq15/a-1 ry/by# http://www..net/ datasheet pdf - http://www..net/ description numonyx? axcell? m29ew 10 208045-11 figure 3. tsop connections 1. a-1 is the least signific ant address bit in x8 mode. 2. a23 is valid for 256-mbit densit y and above; otherwise, it is rfu. 3. a24 is valid for 512-mbit densit y and above; otherwise, it is rfu. 4. a25 is valid for 1-gbit density and above; otherwise, it is rfu. 5. a26 is valid for 2-gbit (1-gbit/1-gbit stack) density only; otherwise it?s rfu. 6. rfu stands for reserved for future use and should be not connect. 56-lead tsop standard pinout 14 mm x 20 mm top view 1 3 4 2 5 7 8 6 9 11 12 10 13 15 16 14 17 19 20 18 21 23 24 22 25 27 28 26 56 54 53 55 52 50 49 51 48 46 45 47 44 42 41 43 40 38 37 39 36 34 33 35 32 30 29 31 a 23 a 21 a 20 ce# a 19 a 17 a 16 a 18 v cc a 14 a 13 a 15 a 12 v pp /wp# a 11 a 9 a 8 a 10 a 6 a 5 a 7 a 4 a 2 a 1 a 3 oe # rst# we# dq 15 / a -1 dq 14 dq 6 dq 7 v ss dq 5 dq 12 dq 13 dq 4 v ss dq 11 v ccq dq 3 dq 2 dq 10 dq 9 dq 8 dq 0 dq 1 a 0 a 22 byte# ry/by# a 26 rfu rfu a 25 a 24 http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew description 208045-11 11 figure 4. fortified bga connections (top and bottom views) 1. a-1 is the least signific ant address bit in x8 mode. 2. a23 is valid for 256-mbit densit y and above; otherwise, it is rfu. 3. a24 is valid for 512-mbit densit y and above; otherwise, it is rfu. 4. a25 is valid for 1-gbit density and above; otherwise, it is rfu. 5. a26 is valid for 2-gbit (1-gbit/1-gbit stack) density only; otherwise it?s rfu. 6. rfu stands for reserved for future use and should be not connect. rfu 1 8 234 5 67 fortified bga top view - ball side down fortified bga bottom view- ball side up 1 8 2 3 4 5 6 7 h g f e d c b a rfu a1 a5 a19 a20 a15 vccq a11 rfu a3 a7 we# ry/by# a13 rfu a9 rfu a2 a6 a21 a18 a14 a23 a10 vss rfu a0 d0 d5 d2 a16 d7 vccq d8 d12 d10 byte# d14 d9 vcc d11 d13 h g f e d c b a a26 a4 a17 rst# vpp/ wp# a12 a22 a8 a26 a4 a17 rst# vpp / wp# a12 a22 a8 rfu vss d1 d4 d3 vss rf u d6 rfu vss d1 d4 d3 vss rfu d6 rfu a2 a6 a21 a18 a14 a23 a10 rfu a1 a5 a19 a20 a15 vccq a11 vss rfu a0 d0 d5 d2 a 16 d7 vccq ce# d8 d12 d10 byte# d14 rfu oe# d9 vcc d11 d15/ a-1 d13 rfu a3 a7 we# a13 rfu a9 a24 a25 d15/ a-1 ce# oe# ry/by# a24 a25 http://www..net/ datasheet pdf - http://www..net/ description numonyx? axcell? m29ew 12 208045-11 figure 5. block addresses 64-kw array block 64-kw array block 64-kw array block 001ffffh 0010000 h 000ffffh 0000000 h 128-kb array block 128-kb array block 128-kb array block 3ffffffh 3 fe0000 h 003ffffh 0020000 h 001ffffh 0000000 h a[26:-1] 2-gbit a[25:-1] 1-gbit a[24:-1] 512-mbit a[23:-1] 256-mbit 64-kw array block 128-kb array block 1 0 511 255 1 0 511 255 512-mbit 64-kw array block 128-kb array block 3ffffffh 3ff0000 h 7ffffffh 7 fe0000 h 1023 1023 1-gbit a[26:0] 2-gbit a[25:0] 1-gbit a[24:0] 512-mbit a[23:0] 256-mbit 256-mbit 1ffffffh 1ff0000 h 0ffffffh 0ff0000 h 1ffffffh 1 fe0000 h 64-kw array block 128-kb array block 7ffffffh 7ff0000 h fffffffh ffe0000 h 2047 2047 2-gbit http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew signal descriptions 208045-11 13 2 signal descriptions see figure 1: logic diagram , and table 1: signal descriptions , for a brief overview of the signals connected to this device. 2.1 address inputs (a0-amax) the address inputs select th e cells in the memory array to access during bus read operations. during bus write operations they control the commands sent to the command interface of the program/erase controller. 2.2 data inputs/outputs (dq0-dq7) the data i/o outputs the data stored at the selected address during a bus read operation. during bus write operations they represent the commands sent to the command interface of the internal state machine. 2.3 data inputs/outputs (dq8-dq14) the data i/o outputs the data stored at the selected address during a bus read operation when byte# is high, v ih . when byte# is low, v il , these pins are not used and are high impedance. during bus write operations the co mmand register does not use these bits. when reading the status register these bits should be ignored. 2.4 data input/output or address input (dq15/a ? 1) when the device operates in x16 bus mode, this pin behaves as a data input/output pin, together with dq8-dq14. when the device operates in x8 bus mode, this pin behaves as the least significant bit of the address. throug hout the text consider references to the data input/output to include this pin when the device operates in x16 bus mode and references to the address inputs to include this pin when the device operates in x8 bus mode except when stated explicitly otherwise. 2.5 chip enable (ce#) the chip enable pin, ce#, activates the memory, allowing bus read and bus write operations to be performed. when chip enable is high, v ih , all other pins are ignored. 2.6 output enable (oe#) the output enable pin, oe#, controls the bus read operation of the memory. http://www..net/ datasheet pdf - http://www..net/ signal descriptions numonyx? axcell? m29ew 14 208045-11 2.7 write enable (we#) the write enable pin, we#, controls the bus write operation of the memory?s command interface. 2.8 v pp /write protect (v pp /wp#) the v pp /write protect pin provides two functions, write protect function and the v pph function, which protect the lowest or highest block and allow the memory to enter unlock bypass mode respectively. the write protect function provides a hardware method of protecting the highest or lowest block (see section 1: description ). when v pp /write protect is low, v il , the highest or lowest block is protected. program and erase operations on this block are ignored while v pp /write protect is low. when v pp /write protect is high, v ih , the memory reverts to the previous protection status of the highest or lowest block. program and erase operations can now modify the data in this block unless the block is protected using block protection. when v pp /write protect is raised to v pph the memory automatically enters the unlock bypass mode (see section 6.2.4 ). when v pp /write protect returns to v ih or v il normal operation resumes. see the description of the unlock bypass command in the command interface section. the transitions from v ih to v pph and from v pph to v ih must be slower than t vhvpp (see figure 28: accelerated program timing waveforms ). never raise v pp /write protect to v pph from any mode except read mode, otherwise the memory may be left in an indeterminate state. a 0.1 f capacitor should be connected between the v pp /write protect pin and the v ss ground pin to decouple the current surges from the power supply. the pcb track widths must be sufficient to carry the currents required during unlock bypass program (see i pp1 , i pp2 , i pp3 , i pp4 in table 22: dc characteristics ). the v pp /write protect pin may be left unconnected as it features an internal pull-up resistor. note: for 2-gbit (1-gbit/1-gbit stack) device, when vpp/wp# pin is low, both the highest block and the lowest block are hardware-protected, namely block 0 and block 2047. refer to ta b l e 2 for a summary of v pp /wp# functions. table 2. v pp /wp# functions v pp /wp# function v il highest block protected or lowest block protected. (1) v ih highest and lowest block unprotected unless a software protection is activated (see section 4: hardware protection ). v pph unlock bypass mode. 1. for 2-gbit (1-gbit/1-gbit stack) device, both the highest block and the lowest block are hardware-protected, namely block 0 and block 2047. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew signal descriptions 208045-11 15 2.9 reset (rst#) the reset pin can be used to apply a hardware reset to the memory. a hardware reset is achieved by holding reset low, v il , for at least t plpx . after reset goes high, v ih , the memory will be ready for bus read and bus write operations after t phel or t rhel , whichever occurs last. see section 2.10: ready/busy output (ry/by#) , ta b l e 2 6 : r e s e t ac characteristics , figure 26 and figure 27 for more details. 2.10 ready/busy output (ry/by#) the ready/busy pin is an open-drain output that can be used to identify when the device is performing a program or erase operation. during program or erase operations ready/busy is low, v ol (see table 17: status register bits ). ready/busy is high-impedance during read mode, auto select mode and erase suspend mode. after a hardware reset, bus read and bus write operations cannot begin until ready/busy becomes high-impedance. see table 26: reset ac characteristics , figure 26 and figure 27 . the use of an open-drain output allows the ready/busy pins from several memories to be connected to a single pull-up resistor. a low val ue will then indicate that one, or more, of the memories is busy. the 10kohm or bigger resistor is recommended as pull-up resistor to achieve 0.1v v ol . 2.11 byte/word organization select (byte#) the byte# pin is used to switch between the x8 and x16 bus modes of the memory. when byte/word organization select is low, v il , the memory is in x8 mode, when it is high, v ih , the memory is in x16 mode. 2.12 v cc supply voltage v cc provides the power supply for all operations (read, program and erase). the command interface is disabled when the v cc supply voltage is less than the lockout voltage, v lko . this prevents bus write operations from accidentally damaging the data during power-up, power-down and power surges. if the program/erase controller is programming or erasing during this time then the operation aborts and the memory contents being altered will be invalid. a 0.1 f capacitor should be connected between the v cc supply voltage pin and the v ss ground pin to decouple the current surges from the power supply. the pcb track widths must be sufficient to carry the currents required during program and erase operations (see i cc1 , i cc2 , i cc3 in table 22: dc characteristics ). 2.13 v ccq input/output supply voltage v ccq provides the power supply to the i/o pins and enables all outputs to be powered independently from v cc . http://www..net/ datasheet pdf - http://www..net/ signal descriptions numonyx? axcell? m29ew 16 208045-11 2.14 v ss ground v ss is the reference for all voltage measurements. the device features two v ss pins; both of which must be connected to the system ground. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew bus operations 208045-11 17 3 bus operations there are five standard bus operations that control the device. these are bus read (random and page modes), bus write, output disable and standby. see table 3: bus operations, 8-bit mode and table 4: bus operations, 16-bit mode for a summary. typical glitches of less than 3ns on chip enable, write enable, and reset pins are ignored by the memory and do not affect bus operations. 3.1 bus read bus read operations read from the memory cells, or specific registers in the command interface. to speed up the read operation the memory array can be read in page mode where data is internally read and stored in a page buffer. the page has a size of 16 words (or 32bytes) and is addressed by the address inputs a3-a0 in x16 bus mode and a3-a0 plus dq15/a ? 1 in x8 bus mode.the page read mode is not supported for reading extended memory blocks and cfi information. a valid bus read operation involves setting the desired address on the address inputs, applying a low signal, v il , to chip enable and output enable and keeping write enable high, v ih . the data inputs/outputs will output the value, see figure 17: random read ac waveforms (8-bit mode) , figure 20: page read ac waveforms (16-bit mode) , and ta bl e 2 3 : read ac characteristics , for details of when the output becomes valid. 3.2 bus write bus write operations write to the command interface. a valid bus write operation begins by setting the desired address on the address inputs. the address inputs are latched by the command interface on the falling edge of chip enable or write enable, whichever occurs last. the data inputs/outputs are latched by the command interface on the rising edge of chip enable or write enable, whichever occurs first. output enable must remain high, v ih , during the whole bus write operation. see figure 21 , and figure 22 , write ac waveforms, and ta b l e 2 4 and ta bl e 2 5 , write ac characteristics, for details of the timing requirements. 3.3 output disable the data inputs/outputs are in the high impedance state when output enable is high, v ih . 3.4 standby driving chip enable high in read mode, causes the memory to enter standby mode and the data inputs/outputs pins are placed in the high-impedance state. to reduce the supply current to the standby supply current, i cc2 , chip enable should be held within v cc 0.3v. for the standby current level see table 22: dc characteristics . during program or erase oper ations the memory will contin ue to use the program/erase supply current, i cc3 , for program or erase operations until the operation completes. http://www..net/ datasheet pdf - http://www..net/ bus operations numonyx? axcell? m29ew 18 208045-11 3.5 reset during reset mode the memory is deselected and the outputs are high impedance. the memory is in reset mode when rst# is at v il . the power consumption is reduced to the standby level, independently from the chip enable, output enable or write enable inputs. 3.6 auto select mode the auto select mode allows the system or the programming equipment to read the electronic signature, verify the protection status of the extended memory block, and apply/remove block protection. for example, this mode can be used by programming equipment to automatically match a device and the application code to be programmed. at power-up, the device is in read mode, and can then be put in auto select mode by issuing the auto select command (see section 6.1.2 ). the device cannot enter auto select mode when a program or erase operation is in progress (ry/by# low). however, auto select mode can be entered if the program or erase operation has been suspended by issuing a program suspend or erase suspend command (see section 6.1.7 ). the auto select mode is exited by performing a reset. the device is returned to read mode, except if the auto select mode was entered after an erase suspend or a program suspend command. in this case, it returns to the erase or program suspend mode. 3.6.1 read electronic signature the memory has two codes, the manufacturer code and the device code used to identify the memory. these codes can be accessed by performing read operations with control signals and addresses set as shown in table 5: read electronic signature - auto select mode - programmer method (8-bit mode) and table 6: read electronic signature - auto select mode - programmer method (16-bit mode) . these codes can also be accessed by issuing an auto select command (see section 6.1.2: auto select command ). 3.6.2 verify extended memory block protection indicator the extended memory block is either numonyx pre-locked or customer-lockable. the protection status of the extended memory block (pre-locked or customer-lockable) can be accessed by reading the extended memory block protection indicator. it can be read in auto select mode using either the programmer (see ta bl e 7 and ta bl e 8 ) or the in-system method (see ta b l e 9 and ta b l e 1 0 ). the protection status of the extended memory block is then output on bit dq7 of the data input/outputs (see ta bl e 3 and ta b l e 4 , bus operations in 8-bit and 16-bit mode). 3.6.3 verify block protection status the protection status of a block can be determined by performing a read operation with control signals and addresses set as shown in ta b l e 7 and ta bl e 8 . if the block is protected, then 01h (in x 8 mode) is output on data input/outputs dq0-dq7, otherwise 00h is output. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew bus operations 208045-11 19 3.6.4 hardware block protect the v pp /wp# pin can be used to protect the highest or lowest block. when v pp /wp# is at v il , the highest block (m29ewh) or the lowest block (m29ewl) is protected and the other blocks remain with their own protection status. http://www..net/ datasheet pdf - http://www..net/ bus operations numonyx? axcell? m29ew 20 208045-11 m table 3. bus operations, 8-bit mode operation (1) ce# oe# we# rst# v pp /wp# address inputs data inputs/outputs amax-a0, dq15/a-1 dq14-dq8 dq7-dq0 bus read v il v il v ih v ih x cell address hi-z data output bus write v il v ih v il v ih v ih (2) command address hi-z data input (3) standby v ih xxv ih v ih x hi-z hi-z output disable v il v ih v ih v ih x x hi-z hi-z reset x x x v il x x hi-z hi-z 1. x = v il or v ih . 2. if wp# is low, v il , the outermost block remains protected. 3. data input as required when issuing a command se quence, performing data polling or block protection. table 4. bus operations, 16-bit mode operation (1) ce# oe# we# rst# v pp /wp# address inputs data inputs/outputs amax-a0 dq15/a-1, dq14-dq0 bus read v il v il v ih v ih x cell address data output bus write v il v ih v il v ih v ih (2) command address data input (3) standby v ih xxv ih v ih x hi-z output disable v il v ih v ih v ih x x hi-z reset x x x v il x x hi-z 1. x = v il or v ih . 2. if wp# is low, v il , the outermost block remains protected. 3. data input as required when issuing a command se quence, performing data polling or block protection. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew bus operations 208045-11 21 table 5. read electronic signature - auto select mode - programmer method (8-bit mode) read cycle (1) ce# oe# we# address inputs data inputs/outputs amax-a4 a3 a2 a1 a0 dq15/a-1 dq14-dq8 dq7-dq0 manufacturer code v il v il v ih v il v il v il v il v il xx 89h device code (cycle 1) v il v il v il v ih xx 7eh device code (cycle 2) v ih v ih v ih v il xx 22h (256-mbit) 23h (512-mbit) 28h (1-gbit) 48h (2-gbit) device code (cycle 3) v ih v ih v ih v ih xx 01h 1. x = v il or v ih . table 6. read electronic signature - auto select mode - programmer method (16-bit mode) read cycle (1) ce# oe# we# address inputs data inputs/outputs amax-a4 a3 a2 a1 a0 dq15/a-1, dq14-dq0 manufacturer code v il v il v ih v il v il v il v il v il 0089h device code (cycle 1) v il v il v il v ih 227eh device code (cycle 2) v ih v ih v ih v il 2222h (256-mbit) 2223h (512-mbit) 2228h (1-gbit) 2248h (2-gbit) device code (cycle 3) v ih v ih v ih v ih 2201h 1. x = v il or v ih . http://www..net/ datasheet pdf - http://www..net/ bus operations numonyx? axcell? m29ew 22 208045-11 table 7. block protection - auto select mode - programmer method (8-bit mode) operation (1) ce# oe# we# address inputs data inputs/outputs amax-a16 a15-a2 a1 a0 dq15/a-1 dq14 -dq8 dq7-dq0 verify extended memory block protection indicator (bit dq7) m29ewl v il v il v ih v il v il v ih v ih xx 89h (numonyx pre- locked) 09h (customer- lockable) m29ewh 99h (numonyx pre- locked) 19h (customer- lockable) verify block protection status bba v il 01h (protected) 00h (unprotected) 1. x = v il or v ih . bba = block base address. table 8. block protection - auto select mode - programmer method (16-bit mode) operation (1) ce# oe# we# address inputs data inputs/outputs amax-a16 a15-a2 a1 a0 dq15/a-1, dq14-dq0 ver ify extended memory block indicator (bit dq7) m29ewl v il v il v ih v il v il v ih v ih 0089h (numonyx pre- locked) 0009h (customer-lockable) m29ewh 0099h (numonyx pre- locked) 0019h (customer-lockable) verify block protection status bba v il 0001h (protected) 0000h (unprotected) 1. x = v il or v ih . bba = block base address. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew hardware protection 208045-11 23 4 hardware protection the m29ew features a v pp /wp# pin that protects the highest or lowest block. refer to section 2: signal descriptions for a detailed description of the signal. 5 software protection the m29ew has four different software protection modes: ? volatile protection ? non-volatile protection ? password protection ? password access on first use all parts default to operate in non-volatile protection mode and the customer is free to activate the non-volatile or the password protection mode. the desired protection mode is activated by setting either the one-time programmable non- volatile protection mode lock bit, or the password protection mode lock bit of the lock register (see section 7.1: lock register ). programming the non-volatile protection mode lock bit or the password protection mode lock bit, to ?0? will permanently activate the non- volatile or the password protection mode, respectively. these two bits are one-time programmable and non-volatile: once the protection mode has been programmed, it cannot be changed and the device will permanently oper ate in the selected protection mode. it is recommended to activate the desired software protection mode when first programming the device. the non-volatile and password protection modes both provide non-volatile protection. volatilely protected blocks and non-volatilely protected blocks can co-exist within the memory array. however, the volatile protection only control the protection scheme for blocks that are not protected using the non-volatile or password protection. if the user attempts to program or erase a protected block, the device ignores the command and returns to read mode. the device is shipped with all blocks unprotec ted. the block protection status can be read either by performing a read electronic signature (see ta b l e 5 and ta bl e 6 ) or by issuing an auto select command (see table 16: block protection status ). for the lowest and highest blocks, an even higher level of block protection can be achieved by locking the blocks using the non-volatile protection and then by holding the v pp /wp# pin low. password access is a security enhancement offered on the m29ew device. this feature protects information stored in the main-array blocks by preventing content alteration or reads until a valid 64-bit password is received . password access may be combined with non- volatile and/or volatile protection to create a multi-tiered solution. please contact your numonyx sales for further details concerning password access feature. http://www..net/ datasheet pdf - http://www..net/ software protection nu monyx? axcell? m29ew 24 208045-11 5.1 volatile protection mode the volatile protection allows the software application to easily protect blocks against inadvertent change. however, the protection can be easily disabled when changes are needed. volatile protection bits, vpbs, are volatile and unique for each block and can be individually modified. vpbs only control the protection scheme for unprotected blocks that have their non-volatile protection bits , nvpbs, cleared (erased to ?1?) (see section 5.2: non- volatile protection mode and section 6.3.5: non-volatile protection mode command set ). by issuing the vpb program or vpb clear co mmands, the vpbs are set (programmed to ?0?) or cleared (erased to ?1?), thus placing associated blocks in the protected or unprotected state respectively. the vpbs can be set (program med to ?0?) or cleared (erased to ?1?) as often as needed. when the parts are first shipped, or after a po wer-up or hardware re set, the vpbs default to be cleared. refer to section 6.3.7 for a description of the volatile protection mode command set. 5.2 non-volatile protection mode 5.2.1 non-volatile protection bits a non-volatile protection bit (nvpb) is assigned to each block. when a nvpb is set to ?0?, the associated block is protected, preventing any program or erase operations in this block. the nvpb bits can be set individually by i ssuing a nvpb program command. they are non- volatile and will remain set through a hardware reset or a power-down/power-up sequence. the nvpbs cannot be cleared individually, they can only be all cleared at the same time by issuing a clear all non-volatile protection bits command. the nvpbs can be protected all at a time by setting a volatile bit, the nvpb lock bit (see section 5.2.2: non-volatile protection bit lock bit ). if one of the non-volatile protected blocks needs to be unprotecte d (correspon ding nvpb set to ?1?), a few more steps are required: 1. first, the nvpb lock bit must be ?1? by either putting the device through a power cycle, or hardware reset. 2. the nvpbs can then be changed to reflect the de sired settings. 3. the nvpb lock bit must be set to ?0? once again to lock the nvpbs by associated command. the device operates normally again. note: 1 to achieve the best prot ection, it is recommended to ex ecute the nvpb lock bit program command early in the boot code and to protect the boot code by holding v pp /wp# low, v il . 2 the nvpbs and vpbs have the same function when v pp /wp# pin is high, v ih , as they do when v pp /wp# pin is at the voltage for program acceleration (v pph ). refer to table 16: block protection status and figure 6: software protection scheme for details on the block protection mechanism, and to section 6.3.5 for a description of the non- volatile protection mode command set. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew software protection 208045-11 25 5.2.2 non-volatile protection bit lock bit the non-volatile protection bit lock bit (nvpb lock bit) is a global volatile bit for all nvpbs. when set (programmed to ?0?), it prevents changing the state of the nvpbs. when reset to ?1?, the nvpbs can be set and reset using the nvpb program command and clear all nvpbs command, respectively. there is only one nvpb lock bit per device. refer to section 6.3.6 for a description of the nvpb lock bit command set. note: 1 no software command unlocks this bit unless the device is in password protection mode; in standard non-volatile protection mode, it can be cleared only by taking the device through a hardware reset or a power-up. 2 the nvpb lock bit must be set (programmed to ?0?) only after all nvpbs are configured to the desired settings. 5.3 password protection mode the password protection mode provides an even higher level of security than the non- volatile protection mode by requiring a 64-bit password for unlocking the device nvpb lock bit. in addition to this password requirement, the nvpb lock bit is set ?0? after power-up and reset to maintain the device in password protection mode. successful execution of the password unlock command by entering the correct passw ord clears the nvpb lock bit, allowing for block nvpbs to be modified. if the password provided is incorrect, the nvpb lock bit remains locked and the state of the nvpbs cannot be modified. to place the device in password protection mode, the following steps are required: 1. prior to activating the password protection mode, it is necessary to set a 64-bit password and to verify it (see password program command and password read command ). password verification is only allowed before the password protection mode is activated. 2. the password protection mode is then activated by programming the password protection mode lock bit to ?0?. this operation is not reversible and once the bit is programmed it cannot be erased, the device permanently remains in password protection mode, and the 64-bit password can neither be retrieved nor reprogrammed. moreover, all commands to the address where the password is stored, are disabled. refer to table 16: block protection status and figure 6: software protection scheme for details on the block protection scheme. refer to section 6.3.4 for a description of the password protection mode command set. note: there is no means to verify the password after password protection mode is enabled. if the password is lost after enabling the password protection mode, there is no way to clear the nvpb lock bit. http://www..net/ datasheet pdf - http://www..net/ software protection nu monyx? axcell? m29ew 26 208045-11 figure 6. software protection scheme 1. nvpbs default to ?1? (block unprotected) when shipped from numonyx. a block is protected or unprotected when its nvpb is set to ?0? and ?1?, respectively. nvpbs are programmed individually and cleared collectively. 2. vpb default status depends on ordering option. a block is prot ected or unprotected when its vpb is set to ?0? and ?1?, respectively. vpbs can be progr ammed and cleared individually. 3. the nvpb lock bit is volatile and default to ?1? (nvpb bits unlocked) after power-up or hardware reset. nvpb bits are locked by setting the nvpb lock bit to ?0?. once programmed to ?0?, the nvpb lock bit can only be reset to ?1? by taking the device through a power-up or hardware reset. ai13676 array block nvpb (1) vpb (2) non-volatile protection mode volatile protection non-volatile protection password protection mode nvpb lock bit (3) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 27 6 command interface all bus write operations to the memory are interpreted by the command interface. commands consist of one or more sequential bus write operations. failure to observe a valid sequence of bus write operations will resu lt in the memory retu rning to read mode. the long command sequences are imposed to maximize data security. the address used for the commands changes depending on whether the memory is in 16- bit or 8-bit mode. note: for 2-gbit (1-gbit/1-gbit) device, all the set-up command should be re-issued to the device when different die is selected. 6.1 standard commands see either ta bl e 9 , or ta b l e 1 0 , depending on the configuration that is being used, for a summary of the standard commands. 6.1.1 read/reset command the device enters read mode of main array memory after a reset or power-up sequence. the read/reset command returns the memory to read mode. it also resets the errors in the status register. either one or three bus write operations can be used to issue the read/reset command. the read/reset command can be issued, between bus write cycles before the start of a program or erase operation, to return the device to read mode. if the read/reset command is issued during the time-out of a block erase op eration, the memory will take up to 10 s to abort. during the abort period no valid data can be read from the memory. the read/reset command will not abort an erase operation wh en issued wh ile in erase suspend. 6.1.2 auto select command the auto select command puts the device in auto select mode, once in auto select mode, the system can read the manufacturer code, the de vice code, the protection status of each block (block protection status) and the extended memory block protection indicator. three consecutive bus write operations are required to issue the auto select command. once the auto select command is issued bus read operations to specific addresses output the manufacturer code, the device code, the extended memory block protection indicator and a block protection status (see ta b l e 9 and ta bl e 1 0 in conjunction with ta bl e 5 , ta b l e 6 , ta bl e 7 , and ta bl e 8 ). the memory remains in auto sele ct mode until a read/reset or cfi query command is issued. http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 28 208045-11 6.1.3 read cfi query command the memory contains an information area, named cfi data structure, which contains a description of various electrical and timing parameters, density information and functions supported by the memory. see appendix b , ta b l e 3 4 , ta bl e 3 5 , table 36, ta bl e 3 7 and table 38 for details on the information contained in the common flash interface (cfi) memory area. the read cfi query command is used to put the memory in read cfi query mode. once in read cfi query mode, bus read operatio ns to the memory will output data from the common flash interface (cfi) memory area. one bus write cycle is required to issue the read cfi query command. this command is va lid only when the devi ce is in the read array or auto select mode. the read/reset command must be issued to return the device to the previous mode (the read array mode or auto select mode). a second read/reset command is required to put the device in read array mo de from auto select mode. 6.1.4 chip erase command the chip erase command can be used to erase the entire chip. six bus write operations are required to issue the chip erase command and start the program/erase controller. if some block are protected, then these are ignored and all the other blocks are erased. if all of the blocks are protected the chip erase operation appears to start but will terminate within about 100 s, leaving the data unchanged. no error condition is given when protected blocks are ignored. during the erase operation the memory will ignore all commands, including the erase suspend command. it is not possible to issue any command to abort the operation. typical chip erase times are given in ta b l e 2 8 . all bus read operations during the chip erase operation will output the stat us register on the da ta inputs/outputs. see section 7.2: status register for more details. after the chip erase operation has complet ed the memory will return to the read mode, unless an error has occurred. when an error oc curs the memory will co ntinue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode. the chip erase command sets all of the bits in unprotected blocks of the memory to ?1?. all previous data is lost. the chip erase operation is aborted by performing a reset or powering down the device. in this case, data integrity cannot be ensured, and it is recommended to erase again the entire chip. 6.1.5 block erase command the block erase command can be used to erase a list of one or more blocks. it sets all of the bits in the unprotected selected blocks to ?1?. all previous data in the selected blocks is lost. six bus write operations are required to select the first block in the list. each additional block in the list can be selected by repeating the sixth bus write operation using the address of the additional block. after the command sequence is written, a block erase time-out occurs. during the time-out period, additional sector addresses and sector erase commands may be written. once the program/erase controller has started, it is not possible to select http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 29 any more blocks. each additional block must therefore be selected within the time-out period of the last block. the time-out timer restarts when an additional block is selected. after the sixth bus write operation, a bus read operation outputs the status register. see figure 21: write enable controlled prog ram waveforms (8-bit mode) and figure 22: write enable controlled program waveforms (16-bit mode) for details on how to identify if the program/erase controller has started the block erase operation. after the block erase operation has completed, the memory returns to the read mode, unless an error has occurred. when an error oc curs, bus read operations will continue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode. if any selected blocks are protected then these are ignored and all the other selected blocks are erased. if all of the selected blocks are protected the block erase operation appears to start but will terminate within about 100 s, leaving the data unchanged. no error condition is given when protected blocks are ignored. during the block erase operation the memory ignores all commands except the erase suspend command and the read/reset command which is only accepted during the time- out period. typical block erase time and block erase time-out are given in ta b l e 2 8 : programming and erase performance . the block erase operation is aborted by performing a reset or powering down the device. in this case, data integrity cannot be ensured, and it is recommended to erase again the blocks aborted. 6.1.6 blank check command the blank check operation determines whether a specified block is blank (i.e. completely erased). without blank check, block erase would be the only other way to ensure a block is completely erased. blank check can be used to determine whether or not a prior erase operation was successful; this includes erase operations that may have been interrupted by power-loss. the blank check operation checks for cells that are programmed as well as cells that are over-erased. if any cells ar e programmed or over-erased, blank check will return a failure status, indicating that the block is not blank. if a blank check operation returns a passing status, the block is guaranteed blank (all 1's) and ready to program. the erase algorithm will do blank check for the target block firstly. if it's blank (all 1's) then the actual erase operation will be skipped. otherwis e, the actual erase operation will continue. this could benefit the overall cycle performance when erase happens on a blank block. blank check can occur in only one block at a time, and no operations other than status register reads are allowed during blank check (e.g. reading array data, program, erase etc). blank check is not supported during any suspended operations. the status register can be examined for blank check progress an d errors by reading any address within the device. after the blank check operati on has completed the memory will return to the read mode, unless an error has occurred. when an error occurs, bus read operations to the memory continue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode. http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 30 208045-11 6.1.7 erase suspend command the erase suspend command can be used to temporarily suspend a block erase operation. one bus write operation is required to issue the command together with the block address. after the command sequence is written, a mi nimum block erase time-out occurs (see section 6.1.7: erase suspend command ). during the time-out period, additional block addresses and block erase commands can be written. the program/erase controller suspends the erase operation within the erase suspend latency time of the erase suspend command being issued. however, when the erase suspend command is written during the block erase time-out, the device immediately terminates the time-out period and suspends the erase operation. once the program/erase controller has stopped, the memory operates in read mode and the erase is suspended. during erase suspend it is possible to read and execute program or write to buffer program operations in blocks that are not suspended; both read and program operations behave as normal on these blocks. reading from blocks that are suspended w ill output the status register. if any attempt is made to program in a protected block or in the suspended block then the program command is ignored and the data remains unchanged. in this case the status register is not read and no error condition is given. it is also possible to issue the auto select, read cfi query and unlock bypass commands during an erase suspend. the read/reset command must be issued to return the device to read array mode before the resume command will be accepted. during erase suspend a bus read operation to the extended memory block will output the extended memory block data. once in the extended memory block mode, the exit extended memory block command must be issued before the erase operation can be resumed. the erase suspend command is ignored if written during chip erase operations. refer to table 28: programming and erase performance for the values of block erase time- out and block erase suspend latency time. if the erase suspend operation is aborted by performing a reset or powering down the device, data integrity cannot be ensured, and it is recommended to erase again the blocks suspended. 6.1.8 erase resume command the erase resume command is used to restart the program/erase controller after an erase suspend. the device must be in read array mode bef ore the resume command will be accepted. an erase can be suspended and resumed more than once. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 31 6.1.9 program suspend command the program suspend command allows the system to interrupt a program operation so that data can be read from any block. when the program suspend command is issued during a program operation, the device suspends the program operation within the program suspend latency time (see table 28: programming and erase performance ) and updates the status register bits. after the program operation has been suspended, the system can read array data from any address. however, data read from program-suspended addresses is not valid. the program suspend command may also be issued during a program operation while an erase is suspended. in this case, data may be read from any addresses not in erase suspend or program suspend. if a read is needed from the extended memory block area (one-time program area), the user must use the proper command sequences to enter and exit this region. the system may also issue the auto select command sequence when the device is in the program suspend mode. the system can read as many auto select codes as required. when the device exits the auto select mode, the device reverts to the program suspend mode, and is ready for another valid operation. see auto select command sequence for more information. if the program suspend operation is aborted by performing a reset or powering down the device, data integrity cannot be ensured, and it is recommended to program again the words or bytes aborted. 6.1.10 program resume command after the program resume command is issued, the device reverts to programming. the controller can determine the status of the program operation using the dq7 or dq6 status bits, just as in the standard program operation. refer to figure 21: write enable controlled program waveforms (8-bit mode) and figure 22: write enable controlled program waveforms (16-bit mode) for details. the system must issue a program resume command, to exit the program suspend mode and to continue the programming operation. further issuing of the resume command is ignored. another program suspend command can be written after the device has resumed programming. 6.1.11 program command the program command can be used to program a value to one address in the memory array at a time. the command requires four bus write operations, the final write operation latches the address and data in the internal state machine and starts the program/erase controller. programming can be suspended and then resumed by issuing a program suspend command and a program resume command, respectively (see section 6.1.9: program suspend command and section 6.1.10: program resume command ). if the address falls in a protected block then the program command is ignored, the data remains unchanged. the status register is ne ver read and no error condition is given. after programming has started, bus read operations output the status register content. see figure 21: write enable controlled program waveforms (8-bit mode) and figure 22: http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 32 208045-11 write enable controlled program waveforms (16-bit mode) for more details. typical program times are given in table 28: programming and erase performance . after the program operat ion has completed the memory will re turn to the read mode, unless an error has occurred. when an error occurs, bus read operations to the memory continue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode. one of the erase commands must be used to set all the bits in a block or in the whole memory from ?0? to ?1?. the program operation is aborted by performing a reset or powering-down the device. in this case data integrity cannot be ensured, and it is recommended to reprogram the word or byte aborted. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 33 table 9. standard commands, 8-bit mode command length bus operations (1) 1st 2nd 3rd 4th 5th 6th add data add data add data add data add data add data read/reset 1x f0- - - - - - - - - - 3 aaa aa 555 55 x f0 - - - - - - auto select manufacturer code 3 aaa aa 555 55 aaa 90 (2)(3) (2)(3) --- - device code extended memory block protection indicator block protection status program (4) 4 aaa aa 555 55 aaa a0 pa pd - - - - chip erase 6 aaa aa 555 55 aaa 80 aaa aa 555 55 aaa 10 block erase 6+ aaa aa 555 55 aaa 80 aaa aa 555 55 bad 30 erase/program suspend 1 x b0 - - - - - - - - - - erase/program resume 1 x 30 - - - - - - - - - - read cfi query 1 aa 98 - - - - - - - - - - blank check setup 6 aaa aa 555 55 bad eb bad 76 bad 00 bad 00 blank check confirm and read 2 bad 29 bad (2) -------- 1. x = don?t care, pa = program address, pd = program data, bad = any address in the block. all values in the table are in hexadecimal. 2. these cells represent read cycles . the other cells are write cycles. 3. the auto select addresses and data are given in table 5: read electronic signature - auto select mode - programmer method (8-bit mode) , and table 7: block protection - auto select mode - programmer method (8-bit mode) , except for a9 that is ?don?t care?. 4. in unlock bypass, the first two unlock cycles are no more needed (see table 11: fast program commands, 8-bit mode and table 12: fast program commands, 16-bit mode ). http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 34 208045-11 table 10. standard commands, 16-bit mode command length bus operations (1) 1st 2nd 3rd 4th 5th 6th add data add data add data add data add data add data read/reset 1x f0- - - - - - - - - - 3555 aa2aa55 x f0 - - - - - - auto select manufacturer code 3 555 aa 2aa 55 555 90 (2)(3) (2)(3) ---- device code extended memory block protection indicator block protection status program (4) 4 555 aa 2aa 55 555 a0 pa pd - - - - chip erase 6 555 aa 2aa 55 555 80 555 aa 2aa 55 555 10 block erase 6+ 555 aa 2aa 55 555 80 555 aa 2aa 55 bad 30 erase/program suspend 1 x b0 - - - - - - - - - - erase/program resume 1 x 30 - - - - - - - - - - read cfi query 1 55 98 - - - - - - - - - - blank check setup 6 555 aa 2aa 55 bad eb bad 76 bad 00 bad 00 blank check confirm and read 2 bad 29 bad (2) -------- 1. x = don?t care, pa = program address, pd = program data, bad = any address in the block. all values in the table are in hexadecimal. 2. these cells represent read cycles . the other cells are write cycles. 3. the auto select addresses and data are given in table 6: read electronic signature - auto select mode - programmer method (16-bit mode) , and table 8: block protection - auto select mode - programmer method (16-bit mode) , except for a9 that is ?don?t care?. 4. in unlock bypass, the first two unlock cycles are no more needed (see table 11 and table 12 fast program commands , 8- bit and 16-bit mode). http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 35 6.2 fast program commands the m29ew offers a set of fast program commands to improve the programming throughput: ? write to buffer program ? unlock bypass see either table 11: fast program commands, 8-bit mode on page 41 or table 12: fast program commands, 16-bit mode on page 41 depending on the configuration that is being used, for a summary of the fast program commands. when v pph is applied to the v pp /write protect pin the memory automatically enters unlock bypass mode (see section 6.2.4: unlock bypass command ). after programming has started, bus read operations in the memory output the status register content. write to buffer program command can be suspended and then resumed by issuing a program suspend command and a program resume command, respectively (see section 6.1.9: prog ram suspend command and section 6.1.10: program resume command ). after the fast program operati on has completed, the memory w ill return to the read mode, unless an error has occurred. when an error occurs bus read operations to the memory will continue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode. one of the erase commands must be used to set all the bits in a block or in the whole memory from ?0? to ?1?. typical program times are given in table 28: programming and erase performance . 6.2.1 write to buffer program command the write to buffer program command makes use of the device?s 512-word program buffer to speed up programming. a maximum of 512 words can be loaded into the program buffer. the write to buffer program command dramatically reduces system programming time compared to the standard non-buffered program command. when issuing a write to buffer program command, the v pp /wp# pin can be either held high, v ih , or raised to v pph . see ta bl e 2 8 for details on typical write to buffer program times in both cases. five successive steps are required to issue the write to buffer program command: 1. the write to buffer program command starts with two unlock cycles. 2. the third bus write cycle sets up the writ e to buffer program command. the set-up code can be addressed to any location within the targeted block. 3. the fourth bus write cycle sets up the number of words/bytes to be programmed. value n is written to the same block address, where n+1 is the number of words/bytes to be programmed. n+1 must not exceed the size of the program buffer or the operation will abort. 4. the fifth cycle loads the first address and data to be programmed. 5. use n bus write cycles to load the address and data for each word/byte into the program buffer. addresses must lie within the range from the start address+1 to the start address + n-1. optimum programming performance and lower power usage are obtained by aligning the starting address at the beginning of a 512-word boundary (a[8:0] = 0x000h). any buffer size smaller than 512-word is allowed within 512-word boundary, while all the addresses used in the write to buffer program operation must http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 36 208045-11 lie within the 512-word boundary. in addition, any cros sing boundary buffer program will result in a program abort. see figure 7 for details of the available program buffer size. to program the content of the program buffer, this command must be followed by a write to buffer program confirm command. if an address is written several times during a write to buffer program operation, the address/data counter will be decr emented at each da ta load operation an d the data will be programmed to the last word loaded into the buffer. invalid address combinations or failing to follow the correct sequence of bus write cycles will abort the write to buffer program. the status register bits dq1, dq5, dq6, dq7 can be used to monitor the device status during a write to buffer program operation. it is possible to detect program operation fails when changing programmed data from ?0? to ?1?, that is when reprogramming data in a portion of memory already programmed. the resulting data will be the logical or between the prev ious value and the current value. see figure 8: write to buffer program fletcher and pseudo code , for a suggested flow chart on using the write to buffer program command. figure 7. boundary condition of program buffer size 512 words 512 words program buffer is allowed 512 words program buffer is allowed any buffer program attempt is not allowed 511 words or less program buffer is allowed 0000h 0200h 0400h 512 words http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 37 figure 8. write to buffer program fletcher and pseudo code 1. n+1 is the number of addresses to be programmed. 2. a write to buffer program abort and reset mu st be issued to return the device in read mode. 3. when the block address is specified, any address in the selected block address space is acceptable. however when write to buffer command, block address ai08968b start write buffer data, start address abort write to buffer fail or abort (5) write n (1) , block address x = 0 write next data, (3) program address pair x = x-1 write to buffer program confirm, block address read status register (dq1, dq5, dq7) at last loaded address yes dq7 = data check status register (dq5, dq7) at last loaded address no yes write to a different block address write to buffer and program aborted (2) dq5 = 1 dq1 = 1 dq7 = data (4) end first three cycles of the write to buffer and program command x=n yes yes yes yes no no no no no http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 38 208045-11 loading program buffer address with data, all addresse s must fall within the selected program buffer page. 4. dq7 must be checked since dq 5 and dq7 may change simultaneously. 5. if this flow chart location is reached bec ause dq5=?1?, then the write to buffer pr ogram command failed. if this flow chart location is reached because dq1=?1?, then the write to buffe r program command aborted. in both cases, the appropriate reset command must be issued to return the device in read mode: a reset command if the operation failed, a write to buffer program abort and reset command if the operation aborted. 6. see table 9 and table 10 , for details on write to buffer program command sequence. 6.2.2 buffered program abort and reset command a buffered program abort and reset command must be issued to abort the buffer program operation and reset the device in read mode. the buffer programming sequence can be aborted in the following ways: ? load a value that is greater than the page buffer size during the number of locations to program step in the write to buffer program command. ? write to an address in a block different than the one specified during the write- buffer-load command. ? write an address/data pair to a different write-buffer-page than the one selected by the starting address during the program buffer data loading stage of the operation. ? write data other than the confirm command after the specified number of data load cycles. the abort condition is indica ted by dq1 = 1, dq7 = dq7 (for the last address location loaded), dq6 = toggle, and dq5 = 0 (all of which are status register bits). a buffered program abort and reset command sequence must be written to reset the device for the next operation. note that the full 3-cycle buffered program abort and reset command sequence is required when using buffer programming features in unlock bypass mode. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 39 6.2.3 write to buffer program confirm command the write to buffer program confirm command is used to confirm a write to buffer program command and to program the n+1 words/bytes loaded in the program buffer by this command. 6.2.4 unlock bypass command the unlock bypass command is used to place the device in unlock bypass mode. when the device enters the unlock bypass mode, the two initial unlock cycles required in the standard program command sequence are no more needed, and only two write cycles are required to program data, instead of the normal four cycles (see note 4 below ta bl e 9 and ta bl e 1 0 ). this results in a faster total programming time. unlock bypass command is consequently used in conjunction with the unlock bypass program command to program the memory faster than with the standard program commands. when the cycle time to the device is long, considerable time saving can be made by using these commands. three bus write operations are required to issue the unlock bypass command. when in unlock bypass mode, only the unlo ck bypass program, unlock bypass block erase, unlock bypass chip erase, and unlock bypass reset commands are valid: ? the unlock bypass program command can be issued to program addresses within the memory. ? the unlock bypass block erase comma nd can then be issued to erase one or more memory blocks. ? the unlock bypass chip erase comm and can be issued to erase the whole memory array. ? the unlock bypass write to buffer program command can be issued to speed up programming operation. ? the unlock bypass reset command can be i ssued to return the memory to read mode. in unlock bypass mode the memory can be read as if in read mode. 6.2.5 unlock bypass program command the unlock bypass program command can be used to program one address in the memory array at a time. the command requires two bus write operations, the final write operation latches the address and data and starts the program/erase controller. the program operation using the unlock bypass program command behaves identically to the program operation using the program command. the operation cannot be aborted, a bus read operation to the memory outputs the status register. see the program command in table 11.: fast program commands, 8-bit mode and table 12.: fast program commands, 16-bit mode for more details. 6.2.6 unlock bypass block erase command the unlock bypass block erase command can be used to erase one or more memory blocks at a time. the command requires two bus write operations instead of six using the standard block erase command. the final bus write operation latches the address of the block and starts the program/erase controller. http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 40 208045-11 to erase multiple block (after the first two bus write operations have selected the first block in the list), each additional block in the list can be selected by repeating the second bus write operation using the address of the additional block. the unlock bypass block erase command behaves in the same way as the block erase command: the operation cannot be aborted, and a bus read operation to the memory outputs the status register (see section 6.1.5: block erase command for details). 6.2.7 unlock bypass chip erase command the unlock bypass chip erase command can be used to erase all memory blocks at a time. the command requires two bus write operations only instead of six using the standard chip erase command. the final bus write operation starts the program/erase controller. the unlock bypass chip erase command behaves in the same way as the chip erase command: the operation cannot be aborted, and a bus read operation to the memory outputs the status register (see section 6.1.4: chip erase command for details). 6.2.8 unlock bypass write to buffer program command the unlock bypass write to buffer command can be used to program the memory in fast program mode. the command requires two bus write operations less than the standard write to buffer program command. the unlock bypass write to buffer program command behaves in the same way as the write to buffer program command: the operation cannot be aborted and a bus read operation to the memory outputs the status register (see section 6.2.1: write to buffer program command for details). the write to buffer program confirm command is used to confirm an unlock bypass write to buffer program command and to program the n+1 words/bytes loaded in the program buffer by this command. 6.2.9 unlock b ypass reset command the unlock bypass reset command can be used to return to read/reset mode from unlock bypass mode. two bus write operations are required to issue the unlock bypass reset command. read/reset command does not exit from unlock bypass mode. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 41 table 11. fast program commands, 8-bit mode command length bus write operations (1) 1st 2nd 3rd 4th 5th add data add data add data add data add data write to buffer program n+5 aaa aa 555 55 bad 25 bad n (2) pa (3) pd write to buffer program confirm 1 bad (4) 29 - - - - - - - - buffered program abort and reset 3 aaa aa 555 55 aaa f0 - - - - unlock bypass 3 aaa aa 555 55 aaa 20 - - - - unlock bypass program 2 x a0 pa pd - - - - - - unlock bypass block erase 2+ x 80 bad 30 - - - - - - unlock bypass chip erase 2x80x10 - - - - - - unlock bypass write to buffer program n+3 bad 25 bad n (2) pa (3) pd - - - - unlock bypass reset 2x90x00 - - - - - - 1. x = don?t care, pa = program address, pd = program data , bad = any address in the block. all values in the table are in hexadecimal. 2. the maximum number of cycles in the buffer prog ram command sequence is 261. the maximum number of cycles in the unlock bypass buffer program command sequ ence is 259. n+1 is the number of bytes to be programmed during the write to buffer program operation. 3. amax-a7 address pin should be cons istently unchanged. a0-a6 and a-1 pins are used to select a byte within the n+1 byte page. 4. bad must be identical to the address loaded durin g the write to buffer program 3rd and 4th cycles. table 12. fast program commands, 16-bit mode command length bus write operations (1) 1st 2nd 3rd 4th 5th add data add data add data add data add data write to buffer program n+5 555 aa 2aa 55 bad 25 bad n (2) pa (3) pd write to buffer program confirm 1 bad (4) 29------ - - buffered program abort and reset 3 555 aa 2aa 55 555 f0 - - - - unlock bypass 3 555 aa 2aa 55 555 20 - - - - http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 42 208045-11 unlock bypass program 2xa0papd- - - - - - unlock bypass block erase 2+ x 80 bad 30 - - - - - - unlock bypass chip erase 2x80x10- - - - - - unlock bypass write to buffer program n+3 bad 25 bad n (2) pa (3) pd - - - - unlock bypass reset 2 x 90 x 00 - - - - - - 1. x = don?t care, pa = program address, pd = program data , bad = any address in the block. all values in the table are in hexadecimal. 2. the maximum number of cycles in the buffer prog ram command sequence is 517. the maximum number of cycles in the unlock bypass buffer program command sequ ence is 515. n+1 is the number of bytes to be programmed during the write to buffer program operation. 3. amax-a9 address pins should be cons istently unchanged. a0-a8 pins are used to select a word within the n+1 word page. 4. bad must be identical to the address loaded durin g the write to buffer program 3rd and 4th cycles. table 12. fast program commands, 16-bit mode command length bus write operations (1) 1st 2nd 3rd 4th 5th add data add data add data add data add data http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 43 6.3 protection commands blocks can be protected individually against ac cidental program, erase or read operations. the device block protection scheme is shown in figure 6: software protection scheme . see either ta b l e 1 3 , or ta b l e 1 4 , depending on the configuration that is being used, for a summary of the block protection commands. block protection commands are available both in 8-bit and 16-bit configuration. the protections of both memory blocks and extended memory block protection are configured through the lock register (see section 7.1: lock register ). 6.3.1 enter extended memory block command the m29ew has one extra 128-word extended memory block that can only be accessed using the enter extended memory block command. three bus write cycles are required to issue the enter extended memory block command. once the command has been issued the device enters the extended memory block mode where all bus read or program operations are conducted on the extended memory block. once the device is in the extended memory block mode, the extended memory block is addressed by using the addresses occupied by block 0 in the other operating modes (see figure 5: block addresses on page 12 ). the device remains in extended memory block mode until the exit extended memory block command is issued or power is removed from the device. after a power-up sequence or hardware reset, th e device will revert to reading from memory blocks in the main array. the extended memory block cannot be erased, and each bit of the extended memory block can only be programmed once. in extended memory block mode, erase, chip erase, erase suspend and erase resume commands are not allowed. to exit from the extended memory block mode the exit extended memory block command must be issued. the extended memory block is protected from further modification by programming lock register bit 0 (see section 7.1: lock register ). once invoked, this protection cannot be undone. 6.3.2 exit extended memory block command the exit extended memory block command is used to exit from the extended memory block mode and return the device to read mode. four bus write operations are required to issue the command. http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 44 208045-11 6.3.3 lock register command set the m29ew offers a set of commands to access the lock register and to configure and verify its content. see the follo wing sections in conjunction with section 7.1: lock register , ta bl e 1 3 and ta bl e 1 4 . enter lock register command set command three bus write cycles are required to issue the enter lock register command set command. once the command has been issued, all bus read or program operations are issued to the lock register. lock register program and lock register read command the lock register program command allows to configure the lock register. the programmed data can then be checked by issuing a lock register read command. an exit protection command set command must then be issued to return the device to read mode (see section 6.3.8: exit protection command set ). 6.3.4 password prot ection mode command set enter password protection command set command three bus write cycles are required to issue the enter password protection command set command. once the command has been issued, the commands related to the password protection mode can be issued to the device. password program command the password program command is used to program the 64-bit password used in the password protection mode. to program the 64-bit password, the complete command sequence must be entered eight times at eight consecutive addresses selected by a1-a0 plus dq15/a-1 in 8-bit mode, or four times at four consecutive addresses selected by a1-a0 in 16-bit mode. the password can be checked by issuing a password read command. once password program operation has completed, an exit protection command set command must be issued to return the device to read mode. the password protection mode can then be selected. by default, all password bits are set to ?1?. note: in order to use password protection feature on 2-gbit (1-gbit/1-gbit stack) device, the password must be programmed to both upper die and bottom die respectively. password read command the password read command is used to verify the password used in password protection mode. to verify the 64-bit password, the complete command sequence must be entered eight times at eight consecutive addresses selected by a1-a0 plus dq15/a-1 in 8-bit mode, or four times at four consecutive addresses selected by a1-a0 in 16-bit mode. if the password mode lock bit is programmed and the user attempts to read the password, the device will output ffh onto the i/o data bus. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 45 an exit protection command set command must be issued to return the device to read mode. password unlock command the password unlock command is used to cl ear the nvpb lock bit allowing to modify the nvpbs. the password unlock command must be issued along with the correct password. there must be a 1 s delay between successive password unlock commands in order to prevent hackers from cracking the password by trying all possible 64-bit combinations. if this delay is not respected, the latest command will be ignored. approximately 1 s is required for unlocking the device after the valid 64-bit password has been provided. 6.3.5 non-volatile pr otection mode command set enter non-volatile protection command set command three bus write cycles are required to issue the enter non-volatile protection command set command. once the command has been issued, the commands related to the non- volatile protection mode can be issued to the device. non-volatile protection bit program command (nvpb program) a block can be protected from program or erase by issuing a non-volatile protection bit command along with the block address. this command sets the nvpb to ?1? for a given block. read non-volatile protection bit status command (read nvpb status) the status of a nvpb for a given block or group of blocks can be read by issuing a read non-volatile modify protection bit command along with the block address. clear all non-volatile protection bits command (clear all nvpbs) the nvpbs are erased simultaneously by issuing a clear all non-volatile protection bits command. no specific block ad dress is required. if the nvpb lock bit is set to ?0?, the command fails. http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 46 208045-11 figure 9. nvpb program/erase algorithm ai14242 yes dq6= toggle no yes no en t e r n vpb command set. pr o g r am nvpb addr = bad read byte twice addr = bad dq5=1 read byte twice addr = bad no yes wait 500 s dq6= toggle read byte twice addr = bad fai l re se t pass dq0= '1'(erase) '0'(program) no ex i t n vpb command set yes http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 47 6.3.6 nvpb lock bit command set enter nvpb lock bit command set command three bus write cycles are required to issue the enter nvpb lock bit command set command. once the command has been issued, the commands allowing to set the nvpb lock bit can be issued to the device. nvpb lock bit program command this command is used to set the nvpb lo ck bit to ?0? thus locking the nvpbs, and preventing them from being modified. read nvpb lock bit status command this command is used to read the status of the nvpb lock bit. 6.3.7 volatile protection mode command set enter volatile protection command set command three bus write cycles are required to issue the enter volatile protection command set command. once the command has been issued, the commands related to the volatile protection mode can be issued to the device. volatile protection bit program command (vpb program) the vpb program command in dividually sets a vpb to ?0? for a given block. if the nvpb for the same block is set, the bloc k is locked regardless of the value of the vpb bit. (see table 16: block protection status ). read vpb status command the status of a vpb for a given block can be read by issuing a re ad vpb status command along with the block address. vpb clear command the vpb clear command individu ally clears (sets to ?1?) the vpb for a given block. if the nvpb for the same block is set, the bloc k is locked regardless of the value of the vpb bit. (see table 16: block protection status ). 6.3.8 exit protection command set the exit protection command set command is used to exit from the lock register, password protection, non-vola tile protection, volatile pr otection, and nvpb lock bit command set mode. it return the device to read mode. http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 48 208045-11 table 13. block protection commands, 8-bit mode (1)(2)(3) command length bus operations 1st 2nd 3rd 4th 5th 6th 7th 8th 9th 10th 11th ad data ad data ad data ad data ad data ad data ad data ad data ad data ad data ad data lock register enter lock register command set (4) 3aaaaa55555aaa40------------ - --- lock register program 2x a0 x data (5) - ------------- - --- lock register read 1 x data (5) - - - ------------- - --- password protection enter password protection command set (4) 3aaaaa55555aaa60------------ - --- password program (6)(7) 2x a0 pwa n pwd n - ------------- - --- password read 8 00 pwd 0 01 pwd 1 02 pw d2 03 pw d3 04 pw d4 05 pw d5 06 pw d6 07 pw d7 - - - - - - password unlock (7) 1 1 00 25 00 03 00 pw d0 01 pw d1 02 pw d2 03 pw d3 04 pw d4 05 pw d5 06 pw d6 07 pw d7 00 29 non-volatile protection enter non- volatile protection command set (4) 3aaaaa55555aaac0------------ - --- nvpb program (8) 2xa0bad00 - ------------- - --- clear all nvpbs (9) 2x 800030 - ------------- - --- read nvpb status (8) 1 bad rd(0)- - - ------------- - --- nvpb lock bit enter nvpb lock bit command set 3aaaaa55555aaa50------------ - --- nvpb lock bit program (8) 2xa0x00 - ------------- - --- read nvpb lock bit status (8) 1 x rd(0)- - - ------------- - --- volatile protection enter volatile protection command set 3aaaaa55555aaae0------------ - --- vpb program (8) 2xa0bad00 - ------------- - --- read vpb status 1 bad rd(0)- - - ------------- - --- vpb clear (8) 2xa0bad01 - ------------- - --- exit protection command set (10) 2x 90 x00 - ------------- - --- enter extended memory block (4) 3aaaaa55555aaa88------------ - --- exit extended memory block 4aaaaa55555aaa90x00---------- - --- http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 49 1. ad = address; dat = data; bad = any address in the block; rd = read data; pwdn = password byte 0 to 7; pwan = password address (n = 0 to 7); x = don?t care . all values in the table are in hexadecimal. 2. grey cells represent read cycles. the other cells are write cycles. 3. dq15 to dq8 are ?don?t care? during unlock and command cycles. amax to a16 are ?don?t care? during unlock and command cycles unless an address is required. 4. an enter command sequence must be issued pr ior to any operation. it disables read and write operations from and to block 0. read and write operations from any other block are allowed. 5. data = lock register content. 6. only one portion of password can be programm ed or read by each password program command. 7. the password portion can be entered or read in any order as long as the entire 64-bit password is entered or read. 8. protected and unprotected states correspond to 00 and 01, respectively. 9. the clear all nvpbs command programs all nvpbs before erasure in order to prev ent the over-erasure of previously cleared non volatile modify protection bits. 10. if an entry command set command is issu ed, an exit protection command set command must be issued to return the device to read mode. http://www..net/ datasheet pdf - http://www..net/ command interface numonyx? axcell? m29ew 50 208045-11 table 14. block protection commands, 16-bit mode (1)(2)(3) command length bus operations 1st 2nd 3rd 4th 5th 6th 7th ad data ad data ad data ad data ad data ad data ad data lock register enter lock register command set (4) 3 555 aa 2aa 55 555 40 - - - - - - - - lock register program 2x a0 xdata (5) - - - ------- lock register read 1 x data (5) ------------ password protection enter password protection command set (4) 3 555 aa 2aa 55 555 60 - - - - - - - - password program (6)(7) 2 x a0 pwan pwdn - - - - - - - - - - password read 4 00 pwd0 01 pwd1 02 pwd2 03 pwd3------ password unlock (7) 7 00 25 00 03 00 pwd0 01 pwd1 02 pwd2 03 pwd3 00 29 non-volatile protection enter non- volatile protection command set (4) 3 555 aa 2aa 55 555 c0 - - - - - - - - nvpb program (8) 2 x a0 bad 00 - - - - - - - - - - clear all nvpbs (9) 2 x 80 00 30 - - - - - - - - - - read nvpb status 1 bad rd(0) - - - - - - - - - - - - nvpb lock bit enter nvpb lock bit command set 3 555 aa 2aa 55 555 50 - - - - - - - - nvpb lock bit program 2xa0 x 00 - - - ------- read nvpb lock bit status 1 x rd(0) - - - - - - - - - - - - volatile protection enter volatile protection command set 3 555 aa 2aa 55 555 e0 - - - - - - - - vpb program 2 x a0 bad 00 - - - - - - - - - - read vpb status 1 bad rd(0) - - - - - - - - - - - - vpb clear 2 x a0 bad 01 - - - - - - - - - - exit protection command set (10) 2x90 x 00 - - - ------- enter extended memory block (4) 3 555 aa 2aa 55 555 88 - - - - - - - - exit extended memory block 4 555 aa 2aa 55 555 90 x 00 - - - - - - http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew command interface 208045-11 51 1. ad = address; dat = data; bad = any address in the block; rd = read data; pwdn = password byte 0 to 3; pwan = password address (n = 0 to 3); x = don?t care . all values in the table are in hexadecimal. 2. grey cells represent read cycles. the other cells are write cycles. 3. dq15 to dq8 are ?don?t care? during unlock and command cycles. amax to a16 are ?don?t care? during unlock and command cycles unless an address is required. 4. an enter command sequence must be issued prior to any operat ion. it disables read and write operations from and to block 0. read and write operations from any other block are allowed. 5. data = lock register content. 6. only one portion of password can be programm ed or read by each password program command. 7. the password portion can be entered or read in any order as long as the entire 64-bit password is entered or read. 8. protected and unprotected states correspond to 00 and 01, respectively. 9. the clear all nvpbs command programs all nvpbs before erasure in order to prev ent the over-erasure of previously cleared non-volatile modify protection bits. 10. if an entry command set command is issu ed, an exit protection command set command must be issued to return the device to read mode. http://www..net/ datasheet pdf - http://www..net/ registers numonyx? axcell? m29ew 52 208045-11 7 registers the device feature two registers: 1. a lock register that allows to configure the memory blocks and extended memory block protection (see table 16: block protection status ) 2. a status register that provides information on the current or previous program or erase operations. 7.1 lock register the lock register is a 16-bit one-time programmable register. the bits in the lock register are summarized in table 15: lock register bits . see section 6.3.3: lock register command set for a description of the commands allowing to read and program the lock register. 7.1.1 password protection mode lock bit (dq2) the password protection mode lock bit, dq0, is one-time programmable. programming (setting to ?0?) this bit permanently places the device in password protection mode. any attempt to program the password protection mode lock bit when the non-volatile protection mode bit is programmed causes the opera tion to abort and the device to return to read mode. 7.1.2 non-volatile protec tion mode lock bit (dq1) the non-volatile protection mode lock bit, dq1, is one-time programmable. programming (setting to ?0?) this bit permanently places the device in non-volatile protection mode. when shipped from numonyx factory, all parts default to operate in non-volatile protection mode. the memory blocks are unprotected (nvpbs set to ?1?). any attempt to program the non-volatile protection mode lock bit when the password protection mode bit is programmed causes the opera tion to abort and the device to return to read mode. 7.1.3 extended memory bl ock protection bit (dq0) if the device is shipped with the extended memory block unlocked, the block can be protected by setting the extended memory block protection bit, dq0, to ?0?. however, this bit is one-time programmable and once protected the extended memory block cannot be unprotected any more. the extended memory block protection status can be read in auto select mode by issuing an auto select command (see ta bl e 9 and ta bl e 1 0 ). http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew registers 208045-11 53 table 15. lock register bits (1) dq15-3 (2) dq2 dq1 dq0 reserved password protection mode lock bit non-volatile protection mode lock bit extended memory block protection bit 1. dq0, dq1 and dq2 lock register bits are set to ?1? when shipped from the numonyx. 2. dq15 to dq3 are reserved and default to ?1?. table 16. block protection status nvpb lock bit (1) block nvpb (2) block vpb (3) block protection status block protection status 1 1 1 00h block unprotected (nvpb changeable) 1 1 0 01h block protected by vpb (nvpb changeable) 1 0 1 01h block protected by nvpb (nvpb changeable) 10001h block protected by nvpb and vpb (nvpb changeable) 0 1 1 00h block unprotected (nvpb unchangeable) 0 1 0 01h block protected by vpb (nvpb unchangeable) 00101h block protected by nvpb (nvpb unchangeable) 00001h block protected by nvpb and vpb (nvpb unchangeable) 1. if the nvpb lock bit is set to ?0?, all nvpbs are locked. if the nvpb lock bit is set to ?1?, all nvpbs are unlocked. 2. if the block nvpb is set to ?0?, the block is protected, if set to ?1?, it is unprotected. 3. if the block vpb is set to ?0?, the block is protected, if set to ?1?, it is unprotected. http://www..net/ datasheet pdf - http://www..net/ registers numonyx? axcell? m29ew 54 208045-11 figure 10. lock register program flowchart 1. pd is the programmed data (see table 15: lock register bits ). 2. each bit of the lock register can only be programmed once. start pass: write lock register exit command: add dont' care, data 90h add dont' care, data 00h ai13677 done yes yes no dq5 = 1 no write unlock cycles: add 555h, data aah add 2aah, data 55h unlock cycle 1 unlock cycle 2 write enter lock register command set: add 555h, data 40h program lock register data: add dont' care, data a0h add dont' care (1) , data pdh polling algorithm device returned to read mode fail reset to return the device to read mode http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew registers 208045-11 55 7.2 status register the m29ew discrete device has one status register. the various bits convey information and errors on the current and previous program/erase operation. bus read operations from any address within the memory, always read the status register during program and erase operations. it is also read during erase suspend when an address within a block being erased is accessed. the bits in the status register are summarized in table 17: status register bits . 7.2.1 data polling bit (dq7) the data polling bit can be used to identify whether the program/erase controller has successfully completed its operation or if it has responded to an erase suspend. the data polling bit is output on dq7 when the status register is read. during program operations the data polling bi t outputs the complement of the bit being programmed to dq7. after successful completion of the program operation the memory returns to read mode and bus read operations, from the address just programmed, output dq7, not its complement. during erase or blank check operations the data polling bit outputs ?0?, the complement of the erased state of dq7. when the algorithm is complete, data polling produces a '1' on dq7. after successful completion of the erase or blank check operation the memory returns to read mode. in erase suspend mode the da ta polling bit will output a ?1? during a bus read operation within a block being erased. the data pollin g bit will change from ?0? to ?1? when the program/erase controller has suspended the erase operation. figure 11: data polling flow chart , gives an example of how to use the data polling bit. a valid address is the address being programmed or an address within the block being erased or blank checked. 7.2.2 toggle bit (dq6) the toggle bit can be used to identify whether the program/erase controller has successfully completed its operation or if it has responded to an erase suspend. the toggle bit is output on dq6 when the status register is read. during a program/erase operation the toggle bit changes from ?0? to ?1? to ?0?, etc., with successive bus read operations at any addres s. after successful completion of the operation the memory returns to read mode. during erase suspend mo de the toggle bit will output when addressing a cell within a block being erased. the toggle bit will stop togglin g when the program/erase controller has suspended the erase operation. figure 12: toggle flow chart , gives an example of how to use the data toggle bit. 7.2.3 error bit (dq5) the error bit can be used to identify errors detected by the program/erase controller. the error bit is set to ?1? when a program, block erase or chip erase operation fails to write the correct data to the memory, or a blank check operation fails. if the error bit is set a http://www..net/ datasheet pdf - http://www..net/ registers numonyx? axcell? m29ew 56 208045-11 read/reset command must be issued before other commands are issued. the error bit is output on dq5 when the status register is read. note that the program command cannot change a bit set to ?0? back to ?1? and attempting to do so will set dq5 to ?1?. a bus read operation to that address will show the bit is still ?0?. one of the erase commands must be used to set all the bits in a block or in the whole memory from ?0? to ?1?. 7.2.4 erase timer bit (dq3) the erase timer bit can be used to identify the start of program/erase controller operation during a block erase command. once the program/erase controller starts erasing the erase timer bit is set to ?1?. before the program/erase controller starts the erase timer bit is set to ?0? and additional blocks to be erased may be written to the command interface. the erase timer bit is output on dq3 when the status register is read. 7.2.5 alternative toggle bit (dq2) the alternative toggle bit can be used to monitor the program/erase controller during erase operations. the alternative toggle bit is output on dq2 when the status register is read. during chip erase and block erase operations the toggle bit changes from ?0? to ?1? to ?0?, etc., with successive bus read operations from addresses within the blocks being erased. a protected block is treated the same as a block not being erased. once the operation completes the memory returns to read mode. during erase suspend the alternative toggle bit changes from ?0? to ?1 ? to ?0?, etc. with successive bus read operations from addresses within the blocks being erased. bus read operations to addresses within blocks not being erased will output the memory array data as if in read mode. 7.2.6 buffered progr am abort bit (dq1) the buffered program abort bit, dq1, is set to ?1? when a buffer program operation aborts. the buffered program abort and reset command must be issued to return the device to read mode (see write to buffer program in section 6.1: standard commands ). for the complete polling flow chart, please refer to figure 13.: status register polling flow chart . http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew registers 208045-11 57 table 17. status register bits (1) operation address dq7 dq6 dq5 dq3 dq2 dq1 ry/by# program (2) any address dq7 toggle 0 ? no toggle 00 program during erase suspend any address dq7 toggle 0 ? ? ? 0 buffered program abort (2) any address dq7 toggle 0 ? ? 1 0 program error any address dq7 toggle 1 ? ? ? hi-z chip erase any address 0 toggle 0 1 toggle ? 0 block erase before timeout erasing block 0 toggle 0 0 toggle ? 0 non-erasing block 0 toggle 0 0 no toggle ?0 block erase/blank check erasing/verifying block 0 toggle 0 1 toggle ? 0 non- erasing/verifying block 0 toggle 0 1 no toggle ?0 erase/blank check suspend erasing/verifying block 1 no toggle 0 ? toggle ? hi-z non- erasing/verifying block data read as normal ? hi-z erase/blank check error any address 0 toggle 1 1 toggle ? hi-z 1. unspecified data bi ts should be ignored. 2. dq7 for buffer program is related to the last address location loaded. http://www..net/ datasheet pdf - http://www..net/ registers numonyx? axcell? m29ew 58 208045-11 figure 11. data polling flow chart read dq5 & dq7 at valid address sta rt rea d d q7 at valid address fail pass ai07760 dq7 = data yes no yes no dq5 = 1 dq7 = data yes no dq = 1 yes no http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew registers 208045-11 59 figure 12. toggle flow chart read dq6 at valid address start read dq6 twice at valid address fail pass ai11530 dq6 = toggle no no yes yes dq5 = 1 no yes dq6 = toggle read dq5 & dq6 at valid address http://www..net/ datasheet pdf - http://www..net/ registers numonyx? axcell? m29ew 60 208045-11 figure 13. status register polling flow chart read 1 read 2 start dq7=valid data? dq5=1? timeout failure device busy , re- poll dq6 toggling? dq1=1? write buffer program abort device busy , re- poll read 3 programming operation? read3 correct data? programming operation complete programming operation failed dq6 toggling? device error dq2 toggling? read1.dq6 read2.dq6 read2.dq6 read3.dq6 read2.dq2 read3.dq2 no yes yes yes no yes no no yes yes no no yes no device in erase/ suspend mode erase complete yes no invalid state use reset comand read 2 read 3 write buffer programming yes no http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew maximum ratings 208045-11 61 8 maximum ratings stressing the device above the rating listed in table 18: absolute maximum ratings may cause permanent damage to the device. exposure to absolute maximum rating conditions for extended periods may affect device relia bility. these are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specification is not implied. refer also to the relevant quality documents from numonyx. table 18. absolute maximum ratings symbol parameter min max unit t bias temperature under bias ? 50 125 c t stg storage temperature ? 65 150 c v io input or output voltage (1)(2) ? 0.6 v cc +0.6 v v cc supply voltage ? 0.6 4 v v ccq input/output supply voltage ? 0.6 4 v v pph (3) program voltage ? 0.6 14.5 v 1. minimum voltage may undershoot to ? 2 v during transition and for less than 20ns during transitions. 2. maximum voltage may overshoot to v cc + 2 v during transition and for le ss than 20ns during transitions. 3. v pph must not remain at 12 v for more than a total of 80hrs. http://www..net/ datasheet pdf - http://www..net/ dc and ac parameters nu monyx? axcell? m29ew 62 208045-11 9 dc and ac parameters this section summarizes the operating measurement conditions, and the dc and ac characteristics of the device. the parameters in the dc and ac characteristics tables that follow, are derived from tests performed under the measurement conditions summarized in table 19: operating and ac measurement conditions . designers should check that the operating conditions in their circuit match the operating conditions when relying on the quoted parameters. figure 14. ac measurement load circuit figure 15. ac measurement i/o waveform table 19. operating and ac measurement conditions parameter min max unit v cc supply voltage 2.7 3.6 v v ccq supply voltage (v ccq v cc )1.653.6v v pp supply voltage -2.0 12.5 v ambient operating temperature ? 40 85 c load capacitance (c l )30pf input rise and fall times 10 ns input pulse voltages 0 to v ccq v input and output timing ref. voltages v ccq /2 v ai05558b c l c l includes jig capacitance device under test 25 k v ccq 25 k v cc 0.1 f v pp 0.1 f ai05557b v ccq 0 v v ccq /2 http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29e w dc and ac parameters 208045-11 63 figure 16. power-up wait timings table 20. power-up wait timings symbol alt. parameter min unit t vchvcqh -v cc (1) high to v ccq (1) high 0 s t vchph (2) t vcs v cc high to rising edge of rst# 300 s t vcqhph (2) t vios v ccq high to rising edge of rst# 0 s t phel t rh rst# high to chip enable low 50 ns t phwl - rst# high to write enable low 150 ns 1. v cc and v ccq ramps must be synchronized during power-up. 2. if rst# is not stable for t vchrh or t vcqhrh , the device does not permit any read and write operati ons and a hardware reset is required. ai14247 v cc rst# t vchph t phel ce# v ccq t vcqhph we# t vchvcqh t phwl http://www..net/ datasheet pdf - http://www..net/ dc and ac parameters nu monyx? axcell? m29ew 64 208045-11 table 21. device capacitance (1) symbol parameter test condition min max unit c in input capacitance for 256-mbit and 512-mbit v in = 0 v 38 pf input capacitance for 1-gbit 4 9 input capacitance for 2-gbit (1-gbit/1-gbit) 8 18 c out output capacitance v out = 0 v 3 6 1. sampled only, not 100% tested. table 22. dc characteristics symbol parameter test condition min typ max unit i li (1) input leakage current 0 v v in v cc --1a i lo output leakage current 0 v v out v cc --1a i cc1 read current random read ce# = v il , oe# = v ih , f=5mhz -2631ma page read ce# = v il , oe# = v ih , f=13mhz -1216ma i cc2 supply current (standby) 256-mbit ce# = v ccq 0.2v, rst# = v ccq 0.2v - 65 210 a 512-mbit - 70 225 1-gbit - 75 240 2-gbit - 150 480 i cc3 (2) supply current (program/erase/blank check) program/erase controller active v pp /wp# = v il or v ih -3550ma v pp /wp#=v pph -3550ma i pp1 v pp current read v pp /wp# v cc -0.25a standby v pp /wp# v cc -215a i pp2 reset rst# = v ss 0.2v -0.25a i pp3 program operation ongoing v pp /wp# = 12 v 5% - 0.05 0.10 ma v pp /wp# = v cc - 0.05 0.10 ma i pp4 erase operation ongoing v pp /wp# = 12 v 5% - 0.05 0.10 ma v pp /wp# = v cc - 0.05 0.10 ma v il input low voltage v cc 2.7 v ? 0.5 - 0.8 v v ih input high voltage v cc 2.7 v 0.7v ccq -v ccq +0.4 v v ol output low voltage i ol = 100 a, v cc =v cc(min) , v ccq =v ccq(min) - - 0.15v ccq v v oh output high voltage i oh = 100 a, v cc =v cc(min) , v ccq =v ccq(min) 0.85v ccq --v v pplk v pp lock-out voltage - - - 0.4 v v pph voltage for v pp /wp# program acceleration - 11.5 - 12.5 v v lko (2) program/erase lockout supply voltage -2.3--v http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29e w dc and ac parameters 208045-11 65 figure 17. random read ac waveforms (8-bit mode) figure 18. random read ac waveforms (16-bit mode) 1. the maximum input leakage current is 5 a on the v pp /wp# pin. 2. sampled only, not 100% tested. ai13698 tavav tavqv taxqx telqx tehqz tglqv tglqx tghqx valid a0-amax/a-1 oe# dq0-dq15 ce# telqv tehqx tghqz valid telbl tblqz byte# ai08970 tavav tavqv taxqx telqx tehqz tglqv tglqx tghqx valid a0-amax oe# dq0-dq7 ce# telqv tehqx tghqz valid telbh byte# http://www..net/ datasheet pdf - http://www..net/ dc and ac parameters nu monyx? axcell? m29ew 66 208045-11 figure 19. byte# transition ac waveform figure 20. page read ac waveforms (16-bit mode) taxqx tbhqv a0-a max byte# tavqv tblqx tblqz valid hi-z a?1 data out data out valid dq0-dq7 dq8-dq15 byte_transition_ac-waveform ai08971 c tehqz tghqx valid a4-amax oe# dq0-dq15 ce# telqv tehqx tghqz valid a0-a3 valid valid valid valid valid valid valid tglqv tavqv t avqv1 valid valid valid valid valid valid table 23. read ac characteristics symbol alt. parameter test condition limit m29ew unit fortified bga tsop t avav t rc address valid to next address valid ce# = v il , oe# = v il min 100 110 ns t avqv t acc address valid to output valid ce# = v il , oe# = v il max 100 110 ns t avqv1 t pag e address valid to output valid (page) ce# = v il , oe# = v il max 25 ns t elqx (1) t lz chip enable low to output transition oe# = v il min 0 ns http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29e w dc and ac parameters 208045-11 67 figure 21. write enable controlled program waveforms (8-bit mode) 1. only the third and fourth cycles of the program command ar e represented. the program command is followed by the check of status register data polling bit and by a read operati on that outputs the data, dout, programmed by the previous t elqv t e chip enable low to output valid oe# = v il max 100 110 ns t glqx (1) t olz output enable low to output transition ce# = v il min 0 ns t glqv t oe output enable low to output valid ce# = v il max 25 ns t ehqz (1) t hz chip enable high to output hi-z oe# = v il max 20 ns t ghqz (1) t df output enable high to output hi-z ce# = v il max 15 ns t ehqx t ghqx t axqx t oh chip enable, output enable or address transition to output transition -min 0 ns t elbl t elbh t elfl t elfh chip enable to byte# low or high - max 10 ns t blqv t flqv byte# low to output valid - max 1 s t bhqv t fhqv byte# high to output valid - max 1 s 1. sampled only, not 100% tested. table 23. read ac characteristics symbol alt. parameter test condition limit m29ew unit fortified bga tsop ai13333 oe# we# a0-amax/ a?1 dq0-dq7 ce# aaah aoh pa pa 3rd cycle 4t h cycle pd dq7 d out d out tavav tavav tavwl twlax data polling read cycle telwl twheh telqv tghwl twlwh twhwl twhwh1 tglqv tdvwh twhdx tghqz taxqx http://www..net/ datasheet pdf - http://www..net/ dc and ac parameters nu monyx? axcell? m29ew 68 208045-11 program command. 2. pa is the address of the memory location to be programmed. pd is the data to be programmed. 3. dq7 is the complement of the data bit being programmed to dq7 (see section 7.2.1: data polling bit (dq7) ). 4. see table 24: write ac characterist ics, write enable controlled , table 25: write ac charac teristics, chip enable controlled and table 23: read ac characteristics for details on the timings. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29e w dc and ac parameters 208045-11 69 figure 22. write enable controlled program waveforms (16-bit mode) 1. only the third and fourth cycles of the program command ar e represented. the program command is followed by the check of status register data polling bit and by a read operati on that outputs the data, dout, programmed by the previous program command. 2. pa is the address of the memory location to be programmed. pd is the data to be programmed. 3. dq7 is the complement of the data bit being programmed to dq7 (see section 7.2.1: data polling bit (dq7) ). 4. see table 24: write ac characterist ics, write enable controlled , table 25: write ac charac teristics, chip enable controlled and table 23: read ac characteristics for details on the timings. ai13699 oe# we# a0-amax dq0-dq15 ce# 555h aoh pa pa 3rd cycle 4th cycle pd dq7 d out d out tavav tavav tavwl twlax data polling read cycle telwl twheh telqv tghwl twlwh twhwl tglqv tdvwh twhdx tghqz taxqx http://www..net/ datasheet pdf - http://www..net/ dc and ac parameters nu monyx? axcell? m29ew 70 208045-11 m table 24. write ac characteristics, write enable controlled symbol alt parameter limit f ortified bga tsop unit t avav t wc address valid to next address valid min 100 110 ns t elwl t cs chip enable low to write enable low min 0 ns t wlwh t wp write enable low to write enable high min 35 ns t dvwh (1) t ds input valid to write enable high min 30 ns t whdx t dh write enable high to input transition min 0 ns t wheh t ch write enable high to chip enable high min 0 ns t whwl t wph write enable high to write enable low min 20 ns t avwl t as address valid to write enable low min 0 ns t wlax t ah write enable low to address transition min 45 ns t ghwl - output enable high to write enable low min 0 ns t whgl t oeh write enable high to output enable low min 0 ns t whrl (2) t busy program/erase valid to ry/by# low max 30 ns t vchel t vcs v cc high to chip enable low min 300 s t whwh1 t whwh1 write buffer program operation (512 words) typ 900 s program operation single word or byte typ 210 s 1. this specification must be complied with by customer?s writi ng timing. any violation to this timing specification may damage the flash device permanently. 2. sampled only, not 100% tested. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29e w dc and ac parameters 208045-11 71 figure 23. chip enable controlled program waveforms (8-bit mode) 1. only the third and fourth cycles of the program command ar e represented. the program command is followed by the check of status register data polling bit. 2. pa is the address of the memory location to be programmed. pd is the data to be programmed. 3. dq7 is the complement of the data bit being programmed to dq7 (see section 7.2.1: data polling bit (dq7) ). 4. see table 24: write ac characteri stics, write enable controlled , table 25: write ac charac teristics, chip enable controlled and table 23: read ac characteristics for details on the timings. ai13334 oe# ce# a0-amax/ a?1 dq0-dq7 we# aaah aoh pa pa 3rd cycle 4t h cycle pd dq7 d out tavav tavel telax data polling twlel tehwh tghel teleh tehel1 twhwh1 tdveh tehdx http://www..net/ datasheet pdf - http://www..net/ dc and ac parameters nu monyx? axcell? m29ew 72 208045-11 figure 24. chip enable controlled program waveforms (16-bit mode) 1. only the third and fourth cycles of the program command ar e represented. the program command is followed by the check of status register data polling bit. 2. pa is the address of the memory location to be programmed. pd is the data to be programmed. 3. dq7 is the complement of the data bit being programmed to dq7 (see section 7.2.1: data polling bit (dq7) ). 4. see table 24: write ac characteri stics, write enable controlled , table 25: write ac charac teristics, chip enable controlled and table 23: read ac characteristics for details on the timings. ai14100 oe# ce# a0-amax dq0-dq15 we# 555h aoh pa pa 3rd cycle 4th cycle pd dq7 d out tavav tavel telax data polling twlel tehwh tghel teleh tehel1 tdveh tehdx http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29e w dc and ac parameters 208045-11 73 figure 25. chip/block erase waveforms (8-bit mode) 1. for a chip erase command, addresses and data are 555h and 10 h, respectively, while they are bad and 30h for a block erase command. 2. bad is the block address. 3. see table 24: write ac characteri stics, write enable controlled , table 25: write ac charac teristics, chip enable controlled and table 23: read ac characteristics for details on the timings. ai13335 oe# we# dq0-dq7 ce# 555h aah 2aah 555h 55h 80h aah tavav tavwl twlax telwl twheh tghwl twlwh twhwl tdvwh twhdx 555h 2aah 555h/bad (1) 55h 10h/ 30h a0-amax/a-1 table 25. write ac characteristics, chip enable controlled symbol alt. parameter limit fortified bga tsop unit t avav t wc address valid to next address valid min 100 110 ns t wlel t ws write enable low to chip enable low min 0 ns t eleh t cp chip enable low to chip enable high min 35 ns t dveh (1) t ds input valid to chip enable high min 30 ns t ehdx t dh chip enable high to input transition min 0 ns t ehwh t wh chip enable high to write enable high min 0 ns t ehel t cph chip enable high to chip enable low min 20 ns t avel t as address valid to chip enable low min 0 ns t elax t ah chip enable low to address transition min 45 ns t ghel - output enable high chip enable low min 0 ns t whwh1 t whwh1 write buffer program operation (512 words) typ 900 s program operation single word or byte typ 210 s 1. this specification must be complied with by customer?s writing timing. the re sult would be unpredictable if there?s any violation to this timing specification. http://www..net/ datasheet pdf - http://www..net/ dc and ac parameters nu monyx? axcell? m29ew 74 208045-11 figure 26. reset ac waveforms (no program/erase in progress) figure 27. reset during program/erase operation ac waveforms ai11300b ry/ by# rst# tplph tphel, tphgl ce#, oe# ai11301b ry/ by# rst# tplph trhel, trhgl ce#, oe# tplrh table 26. reset ac characteristics symbol alt. parame ter min max unit t plrh (1) t ready rst# low to read mode, during program or erase - 32 s t plph t rp rst# pulse width 100 - ns t phel, t phgl (1) t rh rst# high to write enable low, chip enable low, output enable low 50 - ns -t rpd rst# low to standby mode, during read mode 10 - s rst# low to standby mode, during program or erase 50 - s t rhel, t rhgl (1) t rb ry/by# high to write enable low, chip enable low, output enable low 0-ns 1. sampled only, not 100% tested. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29e w dc and ac parameters 208045-11 75 figure 28. accelerated program timing waveforms figure 29. data polling ac waveforms 1. dq7 returns valid data bit when the ongoi ng program or erase command is completed. 2. see table 27: accelerated program and data po lling/data toggle ac characteristics and table 23: read ac characteristics for details on the timings. ai05563 v pp /wp# v pph v il or v ih tvhvpp tvhvpp ai13336c oe# ce# dq7 we# dq6-dq0 data data ry/by# twheh tglqv tehqz tghqz twhgl2 telqv twhrl output flag valid dq7 data valid dq6-dq0 data output flag dq7 dq7 http://www..net/ datasheet pdf - http://www..net/ dc and ac parameters nu monyx? axcell? m29ew 76 208045-11 figure 30. toggle/alternative toggle bit polling ac waveforms (8-bit mode) 1. dq6 stops toggling when the ongoing program or erase comma nd is completed. dq2 stops toggling when the in-progress chip erase or block erase command is completed. 2. see table 27: accelerated program and data po lling/data toggle ac characteristics and table 23: read ac characteristics for details on the timings. ai13337 we# ce# oe# dq6/dq2 toggle toggle toggle stop toggling output valid tghax taxgl tehax tavel tehel2 twhgl2 tghgl2 tghgl2 data ry/by# twhdx tglqv telqv twhrl a0-amax/a-1 table 27. accelerated program and data polling/data toggle ac characteristics symbol alt parameter min max unit t vhvpp -v pp /wp# raising or falling time 250 - ns t axgl t aso address setup time to output enable low during toggle bit polling 15 - ns t ghax, t ehax t aht address hold time from output enable during toggle bit polling 0-ns t ehel2 t eph chip enable high during toggle bit polling 30 - ns t whgl2, t ghgl2 t oeh output hold time during data and toggle bit polling 20 - ns t whrl t busy program/erase valid to ry/by# low - 90 ns http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew programming and erase performance 208045-11 77 10 programming and erase performance table 28. programming and erase performance parameter buffer size byte word min typ (1)(2) max (2) unit block erase (128 kbytes) - - - - 0.8 4 s erase suspend latency time - - - - 27 32 s block erase time-out - - - 50 - - s byte program single byte program - - - - 210 456 s byte write to buffer program 64 64 - - 270 716 s 128 128 - - 310 900 256 256 - - 375 1140 effective write to buffer program per byte 64 1 - - 4.22 11.2 s 128 1 - - 2.42 7.00 256 1 - - 1.46 4.45 word program single word program - - - - 210 456 s word write to buffer program 32 - 32 - 270 716 s 64 - 64 - 310 900 128 - 128 - 375 1140 256 - 256 - 505 1690 512 - 512 - 900 3016 effective write to buffer program per word 32 - 1 - 8.44 22.4 s 64 - 1 - 4.84 14.1 128 - 1 - 2.93 8.90 256 - 1 - 1.97 6.60 512 - 1 - 1.76 5.89 program suspend latency time - - - - 27 32 s blank check - - - - 3.2 - ms program/erase cycles (per block) - - - 100,000 - - cycles erase to suspend (3) ----500-s 1. typical values measured at room temperature and nominal voltages. 2. sampled, but not 100% tested. 3. erase to suspend is a typical time between an initial bl ock erase or erase resume command and the a subsequent erase suspend command. violating the specificat ion repeatedly during any particular bl ock erase may caus e erase failures. http://www..net/ datasheet pdf - http://www..net/ package mechanical specifications numonyx? axcell? m29ew 78 208045-11 11 package mechanical specifications numonyx offers these devices in lead-free tsop, lead-free fortified bga, and leaded fortified bga packages. the category of second level interconnect is marked on the package and on the inner box label, in compliance with jedec standard jesd97. the maximum ratings related to soldering conditions are also marked on the inner box label. figure 31. tsop56 ? 56 lead thin small-outline package, 14 x 20 mm, package outline 1. drawing is not to scale. tsop-b d1 e 1 n cp b e a2 a n/2 d die c l a1 table 29. tsop56 ? 56 lead thin small-outline package, 14 x 20 mm, package mechanical data symbol millimeters inches typ min max typ min max a ? ? 1.20 ? ? 0.047 a1 0.10 0.05 0.15 0.004 0.002 0.006 a2 1.00 0.95 1.05 0.039 0.037 0.041 b (1) 0.22 0.17 0.27 0.0087 0.0067 0.0106 c ? 0.10 0.21 ? 0.004 0.008 cp ? ? 0.10 ? ? 0.004 e 14.00 13.90 14.10 0.551 0.547 0.555 d 20.00 19.80 20.20 0.787 0.780 0.795 d1 18.40 18.30 18.50 0.724 0.720 0.728 e 0.50 ? ? 0.020 ? ? l 0.60 0.50 0.70 0 .024 0.020 0.028 30 530 5 1. for legacy lead width, 0.15mm (typ), 0.10mm (min), 0.20mm (max). http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew package mechanical specifications 208045-11 79 figure 32. fortified bga64 11 x 13 mm - 8 x 8 active ball array, package outline 1. drawing is not to scale. 2. drawing is bottom view. table 30. fortified bga64 11 x 13 mm - 8 x 8 active ball array, package mechanical data symbol millimeters typ min max a? ?1.40 a1 0.49 0.40 ? a2 0.80 ? ? b 0.60 0.55 0.65 d 11.00 10.90 11.10 d1 7.00 ? ? ddd ? ? 0.10 e1.00 ? ? e 13.00 12.90 13.10 e1 7.00 ? ? fd 2.00 ? ? fe 3.00 ? ? sd 0.50 ? ? se 0.50 ? ? e1 e d1 d eb sd se a2 a1 a bga-z23 ddd fd fe ball "a1" http://www..net/ datasheet pdf - http://www..net/ ordering information numonyx? axcell? m29ew 80 208045-11 12 ordering information note: this product is also available with the extended memory block numonyx pre-locked. for further details and ordering information contact your nearest numonyx sales office. devices are shipped from numonyx factory with the memory content bits erased to ?1?. for a list of available options (package, high/low protect, etc.) or for further information on any aspect of the device, please contact your nearest numonyx sales office. table 32. valid combinations of m29ew part numbers note: for further information on ordering products or for product part numbers, go to: http://www.numonyx.com/en-us/memoryproducts/pages/partnumberlookup.aspx. table 31. ordering information scheme example: rc 28f 256 m29ew h * package rc = fortified bga64: 11 x 13 mm, leaded js = tsop56: 14 x 20 mm, lead free, halogen free, rohs compliant pc = fortified bga64: 11 x 13 mm, lead free, halogen free, rohs compliant discrete/scsp 28f= nor parallel interface device density 256=256-mbit 512=512-mbit 00a=1-gbit 00b=2-gbit device type m29ew = 3v core, page, uniform block flash memory device function h = highest block protected by v pp /wp# l = lowest block protected by v pp /wp# device features * = random digit to cover a combination of features, including packing media, special features, and specific customer request information. 256-mbit 512-mbit 1-gbit 2-gbit js28f256m29ewh* js28f512m29ewh* js 28f00am29ewh* js28f00bm29ewh* js28f256m29ewl* js28f512m29ewl* j s28f00am29ewl* pc28f00bm29ewh* pc28f256m29ewh* pc28f512m29ewh* pc28f00am29ewh* rc28f00bm29ewh* pc28f256m29ewl* pc28f512m29ewl* pc28f00am29ewl* rc28f256m29ewh* rc28f512m29ewh* rc28f00am29ewh* rc28f256m29ewl* rc28f512m29ewl* rc28f00am29ewl* http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 81 appendix a memory address table table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) 0 128 / 64 0000000-001ffff 0000000-000ffff 1 128 / 64 0020000-003ffff 0010000-001ffff 2 128 / 64 0040000-005ffff 0020000-002ffff 3 128 / 64 0060000-007ffff 0030000-003ffff 4 128 / 64 0080000-009ffff 0040000-004ffff 5 128 / 64 00a0000-00bffff 0050000-005ffff 6 128 / 64 00c0000-00dffff 0060000-006ffff 7 128 / 64 00e0000-00f ffff 0070000-007ffff 8 128 / 64 0100000-011ffff 0080000-008ffff 9 128 / 64 0120000-013ffff 0090000-009ffff 10 128 / 64 0140000-015ffff 00a0000-00affff 11 128 / 64 0160000-017ffff 00b0000-00bffff 12 128 / 64 0180000-019ffff 00c0000-00cffff 13 128 / 64 01a0000-01bffff 00d0000-00dffff 14 128 / 64 01c0000-01dffff 00e0000-00effff 15 128 / 64 01e0000-01fffff 00f0000-00fffff 16 128 / 64 0200000-021ffff 0100000-010ffff 17 128 / 64 0220000-023ffff 0110000-011ffff 18 128 / 64 0240000-025ffff 0120000-012ffff 19 128 / 64 0260000-027ffff 0130000-013ffff 20 128 / 64 0280000-029ffff 0140000-014ffff 21 128 / 64 02a0000-02bffff 0150000-015ffff 22 128 / 64 02c0000-02dffff 0160000-016ffff 23 128 / 64 02e0000- 02fffff 0170000-017ffff 24 128 / 64 0300000-031ffff 0180000-018ffff 25 128 / 64 0320000-033ffff 0190000-019ffff 26 128 / 64 0340000-035ffff 01a0000-01affff 27 128 / 64 0360000-037ffff 01b0000-01bffff 28 128 / 64 0380000-039ffff 01c0000-01cffff 29 128 / 64 03a0000-03bffff 01d0000-01dffff 30 128 / 64 03c0000-03dffff 01e0000-01effff http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 82 208045-11 31 128 / 64 03e0000-03fffff 01f0000-01fffff 32 128 / 64 0400000-041ffff 0200000-020ffff 33 128 / 64 0420000-043ffff 0210000-021ffff 34 128 / 64 0440000-045ffff 0220000-022ffff 35 128 / 64 0460000-047ffff 0230000-023ffff 36 128 / 64 0480000-049ffff 0240000-024ffff 37 128 / 64 04a0000-04bffff 0250000-025ffff 38 128 / 64 04c0000-04dffff 0260000-026ffff 39 128 / 64 04e0000- 04fffff 0270000-027ffff 40 128 / 64 0500000-051ffff 0280000-028ffff 41 128 / 64 0520000-053ffff 0290000-029ffff 42 128 / 64 0540000-055ffff 02a0000-02affff 43 128 / 64 0560000-057ffff 02b0000-02bffff 44 128 / 64 0580000-059ffff 02c0000-02cffff 45 128 / 64 05a0000-05bffff 02d0000-02dffff 46 128 / 64 05c0000-05dffff 02e0000-02effff 47 128 / 64 05e0000-05fffff 02f0000-02fffff 48 128 / 64 0600000-061ffff 0300000-030ffff 49 128 / 64 0620000-063ffff 0310000-031ffff 50 128 / 64 0640000-065ffff 0320000-032ffff 51 128 / 64 0660000-067ffff 0330000-033ffff 52 128 / 64 0680000-069ffff 0340000-034ffff 53 128 / 64 06a0000-06bffff 0350000-035ffff 54 128 / 64 06c0000-06dffff 0360000-036ffff 55 128 / 64 06e0000- 06fffff 0370000-037ffff 56 128 / 64 0700000-071ffff 0380000-038ffff 57 128 / 64 0720000-073ffff 0390000-039ffff 58 128 / 64 0740000-075ffff 03a0000-03affff 59 128 / 64 0760000-077ffff 03b0000-03bffff 60 128 / 64 0780000-079ffff 03c0000-03cffff 61 128 / 64 07a0000-07bffff 03d0000-03dffff 62 128 / 64 07c0000-07dffff 03e0000-03effff 63 128 / 64 07e0000-07fffff 03f0000-03fffff 64 128 / 64 0800000-081ffff 0400000-040ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 83 65 128 / 64 0820000-083ffff 0410000-041ffff 66 128 / 64 0840000-085ffff 0420000-042ffff 67 128 / 64 0860000-087ffff 0430000-043ffff 68 128 / 64 0880000-089ffff 0440000-044ffff 69 128 / 64 08a0000-08bffff 0450000-045ffff 70 128 / 64 08c0000-08dffff 0460000-046ffff 71 128 / 64 08e0000- 08fffff 0470000-047ffff 72 128 / 64 0900000-091ffff 0480000-048ffff 73 128 / 64 0920000-093ffff 0490000-049ffff 74 128 / 64 0940000-095ffff 04a0000-04affff 75 128 / 64 0960000-097ffff 04b0000-04bffff 76 128 / 64 0980000-099ffff 04c0000-04cffff 77 128 / 64 09a0000-09bffff 04d0000-04dffff 78 128 / 64 09c0000-09dffff 04e0000-04effff 79 128 / 64 09e0000-09fffff 04f0000-04fffff 80 128 / 64 0a00000-0a1ffff 0500000-050ffff 81 128 / 64 0a20000-0a3ffff 0510000-051ffff 82 128 / 64 0a40000-0a5ffff 0520000-052ffff 83 128 / 64 0a60000-0a7ffff 0530000-053ffff 84 128 / 64 0a80000-0a9ffff 0540000-054ffff 85 128 / 64 0aa0000-0abffff 0550000-055ffff 86 128 / 64 0ac0000-0adffff 0560000-056ffff 87 128 / 64 0ae0000-0afffff 0570000-057ffff 88 128 / 64 0b00000-0b1ffff 0580000-058ffff 89 128 / 64 0b20000-0b3ffff 0590000-059ffff 90 128 / 64 0b40000-0b5ffff 05a0000-05affff 91 128 / 64 0b60000-0b7ffff 05b0000-05bffff 92 128 / 64 0b80000-0b9ffff 05c0000-05cffff 93 128 / 64 0ba0000-0bbffff 05d0000-05dffff 94 128 / 64 0bc0000-0bdffff 05e0000-05effff 95 128 / 64 0be0000-0bfffff 05f0000-05fffff 96 128 / 64 0c00000-0c1ffff 0600000-060ffff 97 128 / 64 0c20000-0c3ffff 0610000-061ffff 98 128 / 64 0c40000-0c5ffff 0620000-062ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 84 208045-11 99 128 / 64 0c60000-0c7ffff 0630000-063ffff 100 128 / 64 0c80000-0c9ffff 0640000-064ffff 101 128 / 64 0ca0000-0cbffff 0650000-065ffff 102 128 / 64 0cc0000-0cdffff 0660000-066ffff 103 128 / 64 0ce0000-0cfffff 0670000-067ffff 104 128 / 64 0d00000-0d1ffff 0680000-068ffff 105 128 / 64 0d20000-0d3ffff 0690000-069ffff 106 128 / 64 0d40000-0d5ffff 06a0000-06affff 107 128 / 64 0d60000-0d7ffff 06b0000-06bffff 108 128 / 64 0d80000-0d9ffff 06c0000-06cffff 109 128 / 64 0da0000-0dbffff 06d0000-06dffff 110 128 / 64 0dc0000-0ddffff 06e0000-06effff 111 128 / 64 0de0000-0dfffff 06f0000-06fffff 112 128 / 64 0e00000-0e1ffff 0700000-070ffff 113 128 / 64 0e20000-0e3ffff 0710000-071ffff 114 128 / 64 0e40000-0e5ffff 0720000-072ffff 115 128 / 64 0e60000-0e7ffff 0730000-073ffff 116 128 / 64 0e80000-0e9ffff 0740000-074ffff 117 128 / 64 0ea0000-0ebffff 0750000-075ffff 118 128 / 64 0ec0000-0edffff 0760000-076ffff 119 128 / 64 0ee0000-0efffff 0770000-077ffff 120 128 / 64 0f00000-0f1ffff 0780000-078ffff 121 128 / 64 0f20000-0f3ffff 0790000-079ffff 122 128 / 64 0f40000-0f5ffff 07a0000-07affff 123 128 / 64 0f60000-0f7ffff 07b0000-07bffff 124 128 / 64 0f80000-0f9ffff 07c0000-07cffff 125 128 / 64 0fa0000-0fbffff 07d0000-07dffff 126 128 / 64 0fc0000-0fdffff 07e0000-07effff 127 128 / 64 0fe0000-0f fffff 07f0000-07fffff 128 128 / 64 1000000-101ffff 0800000-080ffff 129 128 / 64 1020000-103ffff 0810000-081ffff 130 128 / 64 1040000-105ffff 0820000-082ffff 131 128 / 64 1060000-107ffff 0830000-083ffff 132 128 / 64 1080000-109ffff 0840000-084ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 85 133 128 / 64 10a0000-10bffff 0850000-085ffff 134 128 / 64 10c0000-10dffff 0860000-086ffff 135 128 / 64 10e0000- 10fffff 0870000-087ffff 136 128 / 64 1100000-111ffff 0880000-088ffff 137 128 / 64 1120000-113ffff 0890000-089ffff 138 128 / 64 1140000-115ffff 08a0000-08affff 139 128 / 64 1160000-117ffff 08b0000-08bffff 140 128 / 64 1180000-119ffff 08c0000-08cffff 141 128 / 64 11a0000-11bffff 08d0000-08dffff 142 128 / 64 11c0000-11dffff 08e0000-08effff 143 128 / 64 11e0000-11fffff 08f0000-08fffff 144 128 / 64 1200000-121ffff 0900000-090ffff 145 128 / 64 1220000-123ffff 0910000-091ffff 146 128 / 64 1240000-125ffff 0920000-092ffff 147 128 / 64 1260000-127ffff 0930000-093ffff 148 128 / 64 1280000-129ffff 0940000-094ffff 149 128 / 64 12a0000-12bffff 0950000-095ffff 150 128 / 64 12c0000-12dffff 0960000-096ffff 151 128 / 64 12e0000- 12fffff 0970000-097ffff 152 128 / 64 1300000-131ffff 0980000-098ffff 153 128 / 64 1320000-133ffff 0990000-099ffff 154 128 / 64 1340000-135ffff 09a0000-09affff 155 128 / 64 1360000-137ffff 09b0000-09bffff 156 128 / 64 1380000-139ffff 09c0000-09cffff 157 128 / 64 13a0000-13bffff 09d0000-09dffff 158 128 / 64 13c0000-13dffff 09e0000-09effff 159 128 / 64 13e0000-13fffff 09f0000-09fffff 160 128 / 64 1400000-141ffff 0a00000-0a0ffff 161 128 / 64 1420000-143ffff 0a10000-0a1ffff 162 128 / 64 1440000-145ffff 0a20000-0a2ffff 163 128 / 64 1460000-147ffff 0a30000-0a3ffff 164 128 / 64 1480000-149ffff 0a40000-0a4ffff 165 128 / 64 14a0000-14bffff 0a50000-0a5ffff 166 128 / 64 14c0000-14dffff 0a60000-0a6ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 86 208045-11 167 128 / 64 14e0000-14fffff 0a70000-0a7ffff 168 128 / 64 1500000-151ffff 0a80000-0a8ffff 169 128 / 64 1520000-153ffff 0a90000-0a9ffff 170 128 / 64 1540000-155ffff 0aa0000-0aaffff 171 128 / 64 1560000-157ffff 0ab0000-0abffff 172 128 / 64 1580000-159ffff 0ac0000-0acffff 173 128 / 64 15a0000-15bffff 0ad0000-0adffff 174 128 / 64 15c0000-15dffff 0ae0000-0aeffff 175 128 / 64 15e0000-15fffff 0af0000-0afffff 176 128 / 64 1600000-161ffff 0b00000-0b0ffff 177 128 / 64 1620000-163ffff 0b10000-0b1ffff 178 128 / 64 1640000-165ffff 0b20000-0b2ffff 179 128 / 64 1660000-167ffff 0b30000-0b3ffff 180 128 / 64 1680000-169ffff 0b40000-0b4ffff 181 128 / 64 16a0000-16bffff 0b50000-0b5ffff 182 128 / 64 16c0000-16dffff 0b60000-0b6ffff 183 128 / 64 16e0000-16fffff 0b70000-0b7ffff 184 128 / 64 1700000-171ffff 0b80000-0b8ffff 185 128 / 64 1720000-173ffff 0b90000-0b9ffff 186 128 / 64 1740000-175ffff 0ba0000-0baffff 187 128 / 64 1760000-177ffff 0bb0000-0bbffff 188 128 / 64 1780000-179ffff 0bc0000-0bcffff 189 128 / 64 17a0000-17bffff 0bd0000-0bdffff 190 128 / 64 17c0000-17dffff 0be0000-0beffff 191 128 / 64 17e0000-17fffff 0bf0000-0bfffff 192 128 / 64 1800000-181ffff 0c00000-0c0ffff 193 128 / 64 1820000-183ffff 0c10000-0c1ffff 194 128 / 64 1840000-185ffff 0c20000-0c2ffff 195 128 / 64 1860000-187ffff 0c30000-0c3ffff 196 128 / 64 1880000-189ffff 0c40000-0c4ffff 197 128 / 64 18a0000-18bffff 0c50000-0c5ffff 198 128 / 64 18c0000-18dffff 0c60000-0c6ffff 199 128 / 64 18e0000-18fffff 0c70000-0c7ffff 200 128 / 64 1900000-191ffff 0c80000-0c8ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 87 201 128 / 64 1920000-193ffff 0c90000-0c9ffff 202 128 / 64 1940000-195ffff 0ca0000-0caffff 203 128 / 64 1960000-197ffff 0cb0000-0cbffff 204 128 / 64 1980000-199ffff 0cc0000-0ccffff 205 128 / 64 19a0000-19bffff 0cd0000-0cdffff 206 128 / 64 19c0000-19dffff 0ce0000-0ceffff 207 128 / 64 19e0000-19fffff 0cf0000-0cfffff 208 128 / 64 1a00000-1a1ffff 0d00000-0d0ffff 209 128 / 64 1a20000-1a3ffff 0d10000-0d1ffff 210 128 / 64 1a40000-1a5ffff 0d20000-0d2ffff 211 128 / 64 1a60000-1a7ffff 0d30000-0d3ffff 212 128 / 64 1a80000-1a9ffff 0d40000-0d4ffff 213 128 / 64 1aa0000-1abffff 0d50000-0d5ffff 214 128 / 64 1ac0000-1adffff 0d60000-0d6ffff 215 128 / 64 1ae0000-1afffff 0d70000-0d7ffff 216 128 / 64 1b00000-1b1ffff 0d80000-0d8ffff 217 128 / 64 1b20000-1b3ffff 0d90000-0d9ffff 218 128 / 64 1b40000-1b5ffff 0da0000-0daffff 219 128 / 64 1b60000-1b7ffff 0db0000-0dbffff 220 128 / 64 1b80000-1b9ffff 0dc0000-0dcffff 221 128 / 64 1ba0000-1bbffff 0dd0000-0ddffff 222 128 / 64 1bc0000-1bdffff 0de0000-0deffff 223 128 / 64 1be0000-1bfffff 0df0000-0dfffff 224 128 / 64 1c00000-1c1ffff 0e00000-0e0ffff 225 128 / 64 1c20000-1c3ffff 0e10000-0e1ffff 226 128 / 64 1c40000-1c5ffff 0e20000-0e2ffff 227 128 / 64 1c60000-1c7ffff 0e30000-0e3ffff 228 128 / 64 1c80000-1c9ffff 0e40000-0e4ffff 229 128 / 64 1ca0000-1cbffff 0e50000-0e5ffff 230 128 / 64 1cc0000-1cdffff 0e60000-0e6ffff 231 128 / 64 1ce0000-1cfffff 0e70000-0e7ffff 232 128 / 64 1d00000-1d1ffff 0e80000-0e8ffff 233 128 / 64 1d20000-1d3ffff 0e90000-0e9ffff 234 128 / 64 1d40000-1d5ffff 0ea0000-0eaffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 88 208045-11 235 128 / 64 1d60000-1d7ffff 0eb0000-0ebffff 236 128 / 64 1d80000-1d9ffff 0ec0000-0ecffff 237 128 / 64 1da0000-1dbffff 0ed0000-0edffff 238 128 / 64 1dc0000-1ddffff 0ee0000-0eeffff 239 128 / 64 1de0000-1dfffff 0ef0000-0efffff 240 128 / 64 1e00000-1e1ffff 0f00000-0f0ffff 241 128 / 64 1e20000-1e3ffff 0f10000-0f1ffff 242 128 / 64 1e40000-1e5ffff 0f20000-0f2ffff 243 128 / 64 1e60000-1e7ffff 0f30000-0f3ffff 244 128 / 64 1e80000-1e9ffff 0f40000-0f4ffff 245 128 / 64 1ea0000-1ebffff 0f50000-0f5ffff 246 128 / 64 1ec0000-1edffff 0f60000-0f6ffff 247 128 / 64 1ee0000-1efffff 0f70000-0f7ffff 248 128 / 64 1f00000-1f1ffff 0f80000-0f8ffff 249 128 / 64 1f20000-1f3ffff 0f90000-0f9ffff 250 128 / 64 1f40000-1f5ffff 0fa0000-0faffff 251 128 / 64 1f60000-1f7ffff 0fb0000-0fbffff 252 128 / 64 1f80000-1f9ffff 0fc0000-0fcffff 253 128 / 64 1fa0000-1fbffff 0fd0000-0fdffff 254 128 / 64 1fc0000-1fdffff 0fe0000-0feffff 255 128 / 64 1fe0000-1f fffff 0ff0000-0ffffff 256 128 / 64 2000000-201ffff 1000000-100ffff 257 128 / 64 2020000-203ffff 1010000-101ffff 258 128 / 64 2040000-205ffff 1020000-102ffff 259 128 / 64 2060000-207ffff 1030000-103ffff 260 128 / 64 2080000-209ffff 1040000-104ffff 261 128 / 64 20a0000-20bffff 1050000-105ffff 262 128 / 64 20c0000-20dffff 1060000-106ffff 263 128 / 64 20e0000- 20fffff 1070000-107ffff 264 128 / 64 2100000-211ffff 1080000-108ffff 265 128 / 64 2120000-213ffff 1090000-109ffff 266 128 / 64 2140000-215ffff 10a0000-10affff 267 128 / 64 2160000-217ffff 10b0000-10bffff 268 128 / 64 2180000-219ffff 10c0000-10cffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 89 269 128 / 64 21a0000-21bffff 10d0000-10dffff 270 128 / 64 21c0000-21dffff 10e0000-10effff 271 128 / 64 21e0000-21fffff 10f0000-10fffff 272 128 / 64 2200000-221ffff 1100000-110ffff 273 128 / 64 2220000-223ffff 1110000-111ffff 274 128 / 64 2240000-225ffff 1120000-112ffff 275 128 / 64 2260000-227ffff 1130000-113ffff 276 128 / 64 2280000-229ffff 1140000-114ffff 277 128 / 64 22a0000-22bffff 1150000-115ffff 278 128 / 64 22c0000-22dffff 1160000-116ffff 279 128 / 64 22e0000- 22fffff 1170000-117ffff 280 128 / 64 2300000-231ffff 1180000-118ffff 281 128 / 64 2320000-233ffff 1190000-119ffff 282 128 / 64 2340000-235ffff 11a0000-11affff 283 128 / 64 2360000-237ffff 11b0000-11bffff 284 128 / 64 2380000-239ffff 11c0000-11cffff 285 128 / 64 23a0000-23bffff 11d0000-11dffff 286 128 / 64 23c0000-23dffff 11e0000-11effff 287 128 / 64 23e0000-23fffff 11f0000-11fffff 288 128 / 64 2400000-241ffff 1200000-120ffff 289 128 / 64 2420000-243ffff 1210000-121ffff 290 128 / 64 2440000-245ffff 1220000-122ffff 291 128 / 64 2460000-247ffff 1230000-123ffff 292 128 / 64 2480000-249ffff 1240000-124ffff 293 128 / 64 24a0000-24bffff 1250000-125ffff 294 128 / 64 24c0000-24dffff 1260000-126ffff 295 128 / 64 24e0000- 24fffff 1270000-127ffff 296 128 / 64 2500000-251ffff 1280000-128ffff 297 128 / 64 2520000-253ffff 1290000-129ffff 298 128 / 64 2540000-255ffff 12a0000-12affff 299 128 / 64 2560000-257ffff 12b0000-12bffff 300 128 / 64 2580000-259ffff 12c0000-12cffff 301 128 / 64 25a0000-25bffff 12d0000-12dffff 302 128 / 64 25c0000-25dffff 12e0000-12effff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 90 208045-11 303 128 / 64 25e0000-25fffff 12f0000-12fffff 304 128 / 64 2600000-261ffff 1300000-130ffff 305 128 / 64 2620000-263ffff 1310000-131ffff 306 128 / 64 2640000-265ffff 1320000-132ffff 307 128 / 64 2660000-267ffff 1330000-133ffff 308 128 / 64 2680000-269ffff 1340000-134ffff 309 128 / 64 26a0000-26bffff 1350000-135ffff 310 128 / 64 26c0000-26dffff 1360000-136ffff 311 128 / 64 26e0000- 26fffff 1370000-137ffff 312 128 / 64 2700000-271ffff 1380000-138ffff 313 128 / 64 2720000-273ffff 1390000-139ffff 314 128 / 64 2740000-275ffff 13a0000-13affff 315 128 / 64 2760000-277ffff 13b0000-13bffff 316 128 / 64 2780000-279ffff 13c0000-13cffff 317 128 / 64 27a0000-27bffff 13d0000-13dffff 318 128 / 64 27c0000-27dffff 13e0000-13effff 319 128 / 64 27e0000-27fffff 13f0000-13fffff 320 128 / 64 2800000-281ffff 1400000-140ffff 321 128 / 64 2820000-283ffff 1410000-141ffff 322 128 / 64 2840000-285ffff 1420000-142ffff 323 128 / 64 2860000-287ffff 1430000-143ffff 324 128 / 64 2880000-289ffff 1440000-144ffff 325 128 / 64 28a0000-28bffff 1450000-145ffff 326 128 / 64 28c0000-28dffff 1460000-146ffff 327 128 / 64 28e0000- 28fffff 1470000-147ffff 328 128 / 64 2900000-291ffff 1480000-148ffff 329 128 / 64 2920000-293ffff 1490000-149ffff 330 128 / 64 2940000-295ffff 14a0000-14affff 331 128 / 64 2960000-297ffff 14b0000-14bffff 332 128 / 64 2980000-299ffff 14c0000-14cffff 333 128 / 64 29a0000-29bffff 14d0000-14dffff 334 128 / 64 29c0000-29dffff 14e0000-14effff 335 128 / 64 29e0000-29fffff 14f0000-14fffff 336 128 / 64 2a00000-2a1ffff 1500000-150ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 91 337 128 / 64 2a20000-2a3ffff 1510000-151ffff 338 128 / 64 2a40000-2a5ffff 1520000-152ffff 339 128 / 64 2a60000-2a7ffff 1530000-153ffff 340 128 / 64 2a80000-2a9ffff 1540000-154ffff 341 128 / 64 2aa0000-2abffff 1550000-155ffff 342 128 / 64 2ac0000-2adffff 1560000-156ffff 343 128 / 64 2ae0000-2afffff 1570000-157ffff 344 128 / 64 2b00000-2b1ffff 1580000-158ffff 345 128 / 64 2b20000-2b3ffff 1590000-159ffff 346 128 / 64 2b40000-2b5ffff 15a0000-15affff 347 128 / 64 2b60000-2b7ffff 15b0000-15bffff 348 128 / 64 2b80000-2b9ffff 15c0000-15cffff 349 128 / 64 2ba0000-2bbffff 15d0000-15dffff 350 128 / 64 2bc0000-2bdffff 15e0000-15effff 351 128 / 64 2be0000-2bfffff 15f0000-15fffff 352 128 / 64 2c00000-2c1ffff 1600000-160ffff 353 128 / 64 2c20000-2c3ffff 1610000-161ffff 354 128 / 64 2c40000-2c5ffff 1620000-162ffff 355 128 / 64 2c60000-2c7ffff 1630000-163ffff 356 128 / 64 2c80000-2c9ffff 1640000-164ffff 357 128 / 64 2ca0000-2cbffff 1650000-165ffff 358 128 / 64 2cc0000-2cdffff 1660000-166ffff 359 128 / 64 2ce0000-2cfffff 1670000-167ffff 360 128 / 64 2d00000-2d1ffff 1680000-068ffff 361 128 / 64 2d20000-2d3ffff 1690000-169ffff 362 128 / 64 2d40000-2d5ffff 16a0000-16affff 363 128 / 64 2d60000-2d7ffff 16b0000-16bffff 364 128 / 64 2d80000-2d9ffff 16c0000-16cffff 365 128 / 64 2da0000-2dbffff 16d0000-16dffff 366 128 / 64 2dc0000-2ddffff 16e0000-16effff 367 128 / 64 2de0000-2dfffff 16f0000-16fffff 368 128 / 64 2e00000-2e1ffff 1700000-170ffff 369 128 / 64 2e20000-2e3ffff 1710000-171ffff 370 128 / 64 2e40000-2e5ffff 1720000-172ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 92 208045-11 371 128 / 64 2e60000-2e7ffff 1730000-173ffff 372 128 / 64 2e80000-2e9ffff 1740000-174ffff 373 128 / 64 2ea0000-2ebffff 1750000-175ffff 374 128 / 64 2ec0000-2edffff 1760000-176ffff 375 128 / 64 2ee0000-2efffff 1770000-177ffff 376 128 / 64 2f00000-2f1ffff 1780000-178ffff 377 128 / 64 2f20000-2f3ffff 1790000-179ffff 378 128 / 64 2f40000-2f5ffff 17a0000-17affff 379 128 / 64 2f60000-2f7ffff 17b0000-17bffff 380 128 / 64 2f80000-2f9ffff 17c0000-17cffff 381 128 / 64 2fa0000-2fbffff 17d0000-17dffff 382 128 / 64 2fc0000-2fdffff 17e0000-17effff 383 128 / 64 2fe0000-2f fffff 17f0000-17fffff 384 128 / 64 3000000-301ffff 1800000-180ffff 385 128 / 64 3020000-303ffff 1810000-181ffff 386 128 / 64 3040000-305ffff 1820000-182ffff 387 128 / 64 3060000-307ffff 1830000-183ffff 388 128 / 64 3080000-309ffff 1840000-184ffff 389 128 / 64 30a0000-30bffff 1850000-185ffff 390 128 / 64 30c0000-30dffff 1860000-186ffff 391 128 / 64 30e0000- 30fffff 1870000-187ffff 392 128 / 64 3100000-311ffff 1880000-188ffff 393 128 / 64 3120000-313ffff 1890000-189ffff 394 128 / 64 3140000-315ffff 18a0000-18affff 395 128 / 64 3160000-317ffff 18b0000-18bffff 396 128 / 64 3180000-319ffff 18c0000-18cffff 397 128 / 64 31a0000-31bffff 18d0000-18dffff 398 128 / 64 31c0000-31dffff 18e0000-18effff 399 128 / 64 31e0000-31fffff 18f0000-18fffff 400 128 / 64 3200000-321ffff 1900000-190ffff 401 128 / 64 3220000-323ffff 1910000-191ffff 402 128 / 64 3240000-325ffff 1920000-192ffff 403 128 / 64 3260000-327ffff 1930000-193ffff 404 128 / 64 3280000-329ffff 1940000-194ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 93 405 128 / 64 32a0000-32bffff 1950000-195ffff 406 128 / 64 32c0000-32dffff 1960000-196ffff 407 128 / 64 32e0000- 32fffff 1970000-197ffff 408 128 / 64 3300000-331ffff 1980000-198ffff 409 128 / 64 3320000-333ffff 1990000-199ffff 410 128 / 64 3340000-335ffff 19a0000-19affff 411 128 / 64 3360000-337ffff 19b0000-19bffff 412 128 / 64 3380000-339ffff 19c0000-19cffff 413 128 / 64 33a0000-33bffff 19d0000-19dffff 414 128 / 64 33c0000-33dffff 19e0000-19effff 415 128 / 64 33e0000-33fffff 19f0000-19fffff 416 128 / 64 3400000-341ffff 1a00000-1a0ffff 417 128 / 64 3420000-343ffff 1a10000-1a1ffff 418 128 / 64 3440000-345ffff 1a20000-1a2ffff 419 128 / 64 3460000-347ffff 1a30000-1a3ffff 420 128 / 64 3480000-349ffff 1a40000-1a4ffff 421 128 / 64 34a0000-34bffff 1a50000-1a5ffff 422 128 / 64 34c0000-34dffff 1a60000-1a6ffff 423 128 / 64 34e0000-34fffff 1a70000-1a7ffff 424 128 / 64 3500000-351ffff 1a80000-1a8ffff 425 128 / 64 3520000-353ffff 1a90000-1a9ffff 426 128 / 64 3540000-355ffff 1aa0000-1aaffff 427 128 / 64 3560000-357ffff 1ab0000-1abffff 428 128 / 64 3580000-359ffff 1ac0000-1acffff 429 128 / 64 35a0000-35bffff 1ad0000-1adffff 430 128 / 64 35c0000-35dffff 1ae0000-1aeffff 431 128 / 64 35e0000-35fffff 1af0000-1afffff 432 128 / 64 3600000-361ffff 1b00000-1b0ffff 433 128 / 64 3620000-363ffff 1b10000-1b1ffff 434 128 / 64 3640000-365ffff 1b20000-1b2ffff 435 128 / 64 3660000-367ffff 1b30000-1b3ffff 436 128 / 64 3680000-369ffff 1b40000-1b4ffff 437 128 / 64 36a0000-36bffff 1b50000-1b5ffff 438 128 / 64 36c0000-36dffff 1b60000-1b6ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 94 208045-11 439 128 / 64 36e0000-36fffff 1b70000-1b7ffff 440 128 / 64 3700000-371ffff 1b80000-1b8ffff 441 128 / 64 3720000-373ffff 1b90000-1b9ffff 442 128 / 64 3740000-375ffff 1ba0000-1baffff 443 128 / 64 3760000-377ffff 1bb0000-1bbffff 444 128 / 64 3780000-379ffff 1bc0000-1bcffff 445 128 / 64 37a0000-37bffff 1bd0000-1bdffff 446 128 / 64 37c0000-37dffff 1be0000-1beffff 447 128 / 64 37e0000-37fffff 1bf0000-1bfffff 448 128 / 64 3800000-381ffff 1c00000-1c0ffff 449 128 / 64 3820000-383ffff 1c10000-1c1ffff 450 128 / 64 3840000-385ffff 1c20000-1c2ffff 451 128 / 64 3860000-387ffff 1c30000-1c3ffff 452 128 / 64 3880000-389ffff 1c40000-1c4ffff 453 128 / 64 38a0000-38bffff 1c50000-1c5ffff 454 128 / 64 38c0000-38dffff 1c60000-1c6ffff 455 128 / 64 38e0000-38fffff 1c70000-1c7ffff 456 128 / 64 3900000-391ffff 1c80000-1c8ffff 457 128 / 64 3920000-393ffff 1c90000-1c9ffff 458 128 / 64 3940000-395ffff 1ca0000-1caffff 459 128 / 64 3960000-397ffff 1cb0000-1cbffff 460 128 / 64 3980000-399ffff 1cc0000-1ccffff 461 128 / 64 39a0000-39bffff 1cd0000-1cdffff 462 128 / 64 39c0000-39dffff 1ce0000-1ceffff 463 128 / 64 39e0000-39fffff 1cf0000-1cfffff 464 128 / 64 3a00000-3a1ffff 1d00000-1d0ffff 465 128 / 64 3a20000-3a3ffff 1d10000-1d1ffff 466 128 / 64 3a40000-3a5ffff 1d20000-1d2ffff 467 128 / 64 3a60000-3a7ffff 1d30000-1d3ffff 468 128 / 64 3a80000-3a9ffff 1d40000-1d4ffff 469 128 / 64 3aa0000-3abffff 1d50000-1d5ffff 470 128 / 64 3ac0000-3adffff 1d60000-1d6ffff 471 128 / 64 3ae0000-3afffff 1d70000-1d7ffff 472 128 / 64 3b00000-3b1ffff 1d80000-1d8ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 95 473 128 / 64 3b20000-3b3ffff 1d90000-1d9ffff 474 128 / 64 3b40000-3b5ffff 1da0000-1daffff 475 128 / 64 3b60000-3b7ffff 1db0000-1dbffff 476 128 / 64 3b80000-3b9ffff 1dc0000-1dcffff 477 128 / 64 3ba0000-3bbffff 1dd0000-1ddffff 478 128 / 64 3bc0000-3bdffff 1de0000-1deffff 479 128 / 64 3be0000-3bfffff 1df0000-1dfffff 480 128 / 64 3c00000-3c1ffff 1e00000-1e0ffff 481 128 / 64 3c20000-3c3ffff 1e10000-1e1ffff 482 128 / 64 3c40000-3c5ffff 1e20000-1e2ffff 483 128 / 64 3c60000-3c7ffff 1e30000-1e3ffff 484 128 / 64 3c80000-3c9ffff 1e40000-1e4ffff 485 128 / 64 3ca0000-3cbffff 1e50000-1e5ffff 486 128 / 64 3cc0000-3cdffff 1e60000-1e6ffff 487 128 / 64 3ce0000-3cfffff 1e70000-1e7ffff 488 128 / 64 3d00000-3d1ffff 1e80000-1e8ffff 489 128 / 64 3d20000-3d3ffff 1e90000-1e9ffff 490 128 / 64 3d40000-3d5ffff 1ea0000-1eaffff 491 128 / 64 3d60000-3d7ffff 1eb0000-1ebffff 492 128 / 64 3d80000-3d9ffff 1ec0000-1ecffff 493 128 / 64 3da0000-3dbffff 1ed0000-1edffff 494 128 / 64 3dc0000-3ddffff 1ee0000-1eeffff 495 128 / 64 3de0000-3dfffff 1ef0000-1efffff 496 128 / 64 3e00000-3e1ffff 1f00000-1f0ffff 497 128 / 64 3e20000-3e3ffff 1f10000-1f1ffff 498 128 / 64 3e40000-3e5ffff 1f20000-1f2ffff 499 128 / 64 3e60000-3e7ffff 1f30000-1f3ffff 500 128 / 64 3e80000-3e9ffff 1f40000-1f4ffff 501 128 / 64 3ea0000-3ebffff 1f50000-1f5ffff 502 128 / 64 3ec0000-3edffff 1f60000-1f6ffff 503 128 / 64 3ee0000-3efffff 1f70000-1f7ffff 504 128 / 64 3f00000-3f1ffff 1f80000-1f8ffff 505 128 / 64 3f20000-3f3ffff 1f90000-1f9ffff 506 128 / 64 3f40000-3f5ffff 1fa0000-1faffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 96 208045-11 507 128 / 64 3f60000-3f7ffff 1fb0000-1fbffff 508 128 / 64 3f80000-3f9ffff 1fc0000-1fcffff 509 128 / 64 3fa0000-3fbffff 1fd0000-1fdffff 510 128 / 64 3fc0000-3fdffff 1fe0000-1feffff 511 128 / 64 3fe0000-3f fffff 1ff0000-1ffffff 512 128 / 64 4000000-401ffff 2000000-200ffff 513 128 / 64 4020000-403ffff 2010000-201ffff 514 128 / 64 4040000-405ffff 2020000-202ffff 515 128 / 64 4060000-407ffff 2030000-203ffff 516 128 / 64 4080000-409ffff 2040000-204ffff 517 128 / 64 40a0000-40bffff 2050000-205ffff 518 128 / 64 40c0000-40dffff 2060000-206ffff 519 128 / 64 40e0000- 40fffff 2070000-207ffff 520 128 / 64 4100000-411ffff 2080000-208ffff 521 128 / 64 4120000-413ffff 2090000-209ffff 522 128 / 64 4140000-415ffff 20a0000-20affff 523 128 / 64 4160000-417ffff 20b0000-20bffff 524 128 / 64 4180000-419ffff 20c0000-20cffff 525 128 / 64 41a0000-41bffff 20d0000-20dffff 526 128 / 64 41c0000-41dffff 20e0000-20effff 527 128 / 64 41e0000-41fffff 20f0000-20fffff 528 128 / 64 4200000-421ffff 2100000-210ffff 529 128 / 64 4220000-423ffff 2110000-211ffff 530 128 / 64 4240000-425ffff 2120000-212ffff 531 128 / 64 4260000-427ffff 2130000-213ffff 532 128 / 64 4280000-429ffff 2140000-214ffff 533 128 / 64 42a0000-42bffff 2150000-215ffff 534 128 / 64 42c0000-42dffff 2160000-216ffff 535 128 / 64 42e0000- 42fffff 2170000-217ffff 536 128 / 64 4300000-431ffff 2180000-218ffff 537 128 / 64 4320000-433ffff 2190000-219ffff 538 128 / 64 4340000-435ffff 21a0000-21affff 539 128 / 64 4360000-437ffff 21b0000-21bffff 540 128 / 64 4380000-439ffff 21c0000-21cffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 97 541 128 / 64 43a0000-43bffff 21d0000-21dffff 542 128 / 64 43c0000-43dffff 21e0000-21effff 543 128 / 64 43e0000-43fffff 21f0000-21fffff 544 128 / 64 4400000-441ffff 2200000-220ffff 545 128 / 64 4420000-443ffff 2210000-221ffff 546 128 / 64 4440000-445ffff 2220000-222ffff 547 128 / 64 4460000-447ffff 2230000-223ffff 548 128 / 64 4480000-449ffff 2240000-224ffff 549 128 / 64 44a0000-44bffff 2250000-225ffff 550 128 / 64 44c0000-44dffff 2260000-226ffff 551 128 / 64 44e0000- 44fffff 2270000-227ffff 552 128 / 64 4500000-451ffff 2280000-228ffff 553 128 / 64 4520000-453ffff 2290000-229ffff 554 128 / 64 4540000-455ffff 22a0000-22affff 555 128 / 64 4560000-457ffff 22b0000-22bffff 556 128 / 64 4580000-459ffff 22c0000-22cffff 557 128 / 64 45a0000-45bffff 22d0000-22dffff 558 128 / 64 45c0000-45dffff 22e0000-22effff 559 128 / 64 45e0000-45fffff 22f0000-22fffff 560 128 / 64 4600000-461ffff 2300000-230ffff 561 128 / 64 4620000-463ffff 2310000-231ffff 562 128 / 64 4640000-465ffff 2320000-232ffff 563 128 / 64 4660000-467ffff 2330000-233ffff 564 128 / 64 4680000-469ffff 2340000-234ffff 565 128 / 64 46a0000-46bffff 2350000-235ffff 566 128 / 64 46c0000-46dffff 2360000-236ffff 567 128 / 64 46e0000- 46fffff 2370000-237ffff 568 128 / 64 4700000-471ffff 2380000-238ffff 569 128 / 64 4720000-473ffff 2390000-239ffff 570 128 / 64 4740000-475ffff 23a0000-23affff 571 128 / 64 4760000-477ffff 23b0000-23bffff 572 128 / 64 4780000-479ffff 23c0000-23cffff 573 128 / 64 47a0000-47bffff 23d0000-23dffff 574 128 / 64 47c0000-47dffff 23e0000-23effff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 98 208045-11 575 128 / 64 47e0000-47fffff 23f0000-23fffff 576 128 / 64 4800000-481ffff 2400000-240ffff 577 128 / 64 4820000-483ffff 2410000-241ffff 578 128 / 64 4840000-485ffff 2420000-242ffff 579 128 / 64 4860000-487ffff 2430000-243ffff 580 128 / 64 4880000-489ffff 2440000-244ffff 581 128 / 64 48a0000-48bffff 2450000-245ffff 582 128 / 64 48c0000-48dffff 2460000246ffff 583 128 / 64 48e0000- 48fffff 2470000-247ffff 584 128 / 64 4900000-491ffff 2480000-248ffff 585 128 / 64 4920000-493ffff 2490000-249ffff 586 128 / 64 4940000-495ffff 24a0000-24affff 587 128 / 64 4960000-497ffff 24b0000-24bffff 588 128 / 64 4980000-499ffff 24c0000-24cffff 589 128 / 64 49a0000-49bffff 24d0000-24dffff 590 128 / 64 49c0000-49dffff 24e0000-24effff 591 128 / 64 49e0000-49fffff 24f0000-24fffff 592 128 / 64 4a00000-4a1ffff 2500000-250ffff 593 128 / 64 4a20000-4a3ffff 2510000-251ffff 594 128 / 64 4a40000-4a5ffff 2520000-252ffff 595 128 / 64 4a60000-4a7ffff 2530000-253ffff 596 128 / 64 4a80000-4a9ffff 2540000-254ffff 597 128 / 64 4aa0000-4abffff 2550000-255ffff 598 128 / 64 4ac0000-4adffff 2560000-256ffff 599 128 / 64 4ae0000-4afffff 2570000-257ffff 600 128 / 64 4b00000-4b1ffff 2580000-258ffff 601 128 / 64 4b20000-4b3ffff 2590000-259ffff 602 128 / 64 4b40000-4b5ffff 25a0000-25affff 603 128 / 64 4b60000-4b7ffff 25b0000-25bffff 604 128 / 64 4b80000-4b9ffff 25c0000-25cffff 605 128 / 64 4ba0000-4bbffff 25d0000-25dffff 606 128 / 64 4bc0000-4bdffff 25e0000-25effff 607 128 / 64 4be0000-4bfffff 25f0000-25fffff 608 128 / 64 4c00000-4c1ffff 2600000-260ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 99 609 128 / 64 4c20000-4c3ffff 2610000-261ffff 610 128 / 64 4c40000-4c5ffff 2620000-262ffff 611 128 / 64 4c60000-4c7ffff 2630000-263ffff 612 128 / 64 4c80000-4c9ffff 2640000-264ffff 613 128 / 64 4ca0000-4cbffff 2650000-265ffff 614 128 / 64 4cc0000-4cdffff 2660000-266ffff 615 128 / 64 4ce0000-4cfffff 2670000-267ffff 616 128 / 64 4d00000-4d1ffff 2680000-268ffff 617 128 / 64 4d20000-4d3ffff 2690000-269ffff 618 128 / 64 4d40000-4d5ffff 26a0000-26affff 619 128 / 64 4d60000-4d7ffff 26b0000-26bffff 620 128 / 64 4d80000-4d9ffff 26c0000-26cffff 621 128 / 64 4da0000-4dbffff 26d0000-26dffff 622 128 / 64 4dc0000-4ddffff 26e0000-26effff 623 128 / 64 4de0000-4dfffff 26f0000-26fffff 624 128 / 64 4e00000-4e1ffff 2700000-270ffff 625 128 / 64 4e20000-4e3ffff 2710000-271ffff 626 128 / 64 4e40000-4e5ffff 2720000-272ffff 627 128 / 64 4e60000-4e7ffff 2730000-273ffff 628 128 / 64 4e80000-4e9ffff 2740000-274ffff 629 128 / 64 4ea0000-4ebffff 2750000-275ffff 630 128 / 64 4ec0000-4edffff 2760000-276ffff 631 128 / 64 4ee0000-4efffff 2770000-277ffff 632 128 / 64 4f00000-4f1ffff 2780000-278ffff 633 128 / 64 4f20000-4f3ffff 2790000-279ffff 634 128 / 64 4f40000-4f5ffff 27a0000-27affff 635 128 / 64 4f60000-4f7ffff 27b0000-27bffff 636 128 / 64 4f80000-4f9ffff 27c0000-27cffff 637 128 / 64 4fa0000-4fbffff 27d0000-27dffff 638 128 / 64 4fc0000-4fdffff 27e0000-27effff 639 128 / 64 4fe0000-4f fffff 27f0000-27fffff 640 128 / 64 5000000-501ffff 2800000-280ffff 641 128 / 64 5020000-503ffff 2810000-281ffff 642 128 / 64 5040000-505ffff 2820000-282ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 100 208045-11 643 128 / 64 5060000-507ffff 2830000-283ffff 644 128 / 64 5080000-509ffff 2840000-284ffff 645 128 / 64 50a0000-50bffff 2850000-285ffff 646 128 / 64 50c0000-50dffff 2860000-286ffff 647 128 / 64 50e0000- 50fffff 2870000-287ffff 648 128 / 64 5100000-511ffff 2880000-288ffff 649 128 / 64 5120000-513ffff 2890000-289ffff 650 128 / 64 5140000-515ffff 28a0000-28affff 651 128 / 64 5160000-517ffff 28b0000-28bffff 652 128 / 64 5180000-519ffff 28c0000-28cffff 653 128 / 64 51a0000-51bffff 28d0000-28dffff 654 128 / 64 51c0000-51dffff 28e0000-28effff 655 128 / 64 51e0000-51fffff 28f0000-28fffff 656 128 / 64 5200000-521ffff 2900000-290ffff 657 128 / 64 5220000-523ffff 2910000-291ffff 658 128 / 64 5240000-525ffff 2920000-292ffff 659 128 / 64 5260000-527ffff 2930000-293ffff 660 128 / 64 5280000-529ffff 2940000-294ffff 661 128 / 64 52a0000-52bffff 2950000-295ffff 662 128 / 64 52c0000-52dffff 2960000-296ffff 663 128 / 64 52e0000- 52fffff 2970000-297ffff 664 128 / 64 5300000-531ffff 2980000-298ffff 665 128 / 64 5320000-533ffff 2990000-299ffff 666 128 / 64 5340000-535ffff 29a0000-29affff 667 128 / 64 5360000-537ffff 29b0000-29bffff 668 128 / 64 5380000-539ffff 29c0000-29cffff 669 128 / 64 53a0000-53bffff 29d0000-29dffff 670 128 / 64 53c0000-53dffff 29e0000-29effff 671 128 / 64 53e0000-53fffff 29f0000-29fffff 672 128 / 64 5400000-541ffff 2a00000-2a0ffff 673 128 / 64 5420000-543ffff 2a10000-2a1ffff 674 128 / 64 5440000-545ffff 2a20000-2a2ffff 675 128 / 64 5460000-547ffff 2a30000-2a3ffff 676 128 / 64 5480000-549ffff 2a40000-2a4ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 101 677 128 / 64 54a0000-54bffff 2a50000-2a5ffff 678 128 / 64 54c0000-54dffff 2a60000-2a6ffff 679 128 / 64 54e0000-54fffff 2a70000-2a7ffff 680 128 / 64 5500000-551ffff 2a80000-2a8ffff 681 128 / 64 5520000-553ffff 2a90000-2a9ffff 682 128 / 64 5540000-555ffff 2aa0000-2aaffff 683 128 / 64 5560000-557ffff 2ab0000-2abffff 684 128 / 64 5580000-559ffff 2ac0000-2acffff 685 128 / 64 55a0000-55bffff 2ad0000-2adffff 686 128 / 64 55c0000-55dffff 2ae0000-2aeffff 687 128 / 64 55e0000-55fffff 2af0000-2afffff 688 128 / 64 5600000-561ffff 2b00000-2b0ffff 689 128 / 64 5620000-563ffff 2b10000-2b1ffff 690 128 / 64 5640000-565ffff 2b20000-2b2ffff 691 128 / 64 5660000-567ffff 2b30000-2b3ffff 692 128 / 64 5680000-569ffff 2b40000-2b4ffff 693 128 / 64 56a0000-56bffff 2b50000-2b5ffff 694 128 / 64 56c0000-56dffff 2b60000-2b6ffff 695 128 / 64 56e0000-56fffff 2b70000-2b7ffff 696 128 / 64 5700000-571ffff 2b80000-2b8ffff 697 128 / 64 5720000-573ffff 2b90000-2b9ffff 698 128 / 64 5740000-575ffff 2ba0000-2baffff 699 128 / 64 5760000-577ffff 2bb0000-2bbffff 700 128 / 64 5780000-579ffff 2bc0000-2bcffff 701 128 / 64 57a0000-57bffff 2bd0000-2bdffff 702 128 / 64 57c0000-57dffff 2be0000-2beffff 703 128 / 64 57e0000-57fffff 2bf0000-2bfffff 704 128 / 64 5800000-581ffff 2c00000-2c0ffff 705 128 / 64 5820000-583ffff 2c10000-2c1ffff 706 128 / 64 5840000-585ffff 2c20000-2c2ffff 707 128 / 64 5860000-587ffff 2c30000-2c3ffff 708 128 / 64 5880000-589ffff 2c40000-2c4ffff 709 128 / 64 58a0000-58bffff 2c50000-2c5ffff 710 128 / 64 58c0000-58dffff 2c60000-2c6ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 102 208045-11 711 128 / 64 58e0000-58fffff 2c70000-2c7ffff 712 128 / 64 5900000-591ffff 2c80000-2c8ffff 713 128 / 64 5920000-593ffff 2c90000-2c9ffff 714 128 / 64 5940000-595ffff 2ca0000-2caffff 715 128 / 64 5960000-597ffff 2cb0000-2cbffff 716 128 / 64 5980000-599ffff 2cc0000-2ccffff 717 128 / 64 59a0000-59bffff 2cd0000-2cdffff 718 128 / 64 59c0000-59dffff 2ce0000-2ceffff 719 128 / 64 59e0000-59fffff 2cf0000-2cfffff 720 128 / 64 5a00000-5a1ffff 2d00000-2d0ffff 721 128 / 64 5a20000-5a3ffff 2d10000-2d1ffff 722 128 / 64 5a40000-5a5ffff 2d20000-2d2ffff 723 128 / 64 5a60000-5a7ffff 2d30000-2d3ffff 724 128 / 64 5a80000-5a9ffff 2d40000-2d4ffff 725 128 / 64 5aa0000-5abffff 2d50000-2d5ffff 726 128 / 64 5ac0000-5adffff 2d60000-2d6ffff 727 128 / 64 5ae0000-5afffff 2d70000-2d7ffff 728 128 / 64 5b00000-5b1ffff 2d80000-2d8ffff 729 128 / 64 5b20000-5b3ffff 2d90000-2d9ffff 730 128 / 64 5b40000-5b5ffff 2da0000-2daffff 731 128 / 64 5b60000-5b7ffff 2db0000-2dbffff 732 128 / 64 5b80000-5b9ffff 2dc0000-2dcffff 733 128 / 64 5ba0000-5bbffff 2dd0000-2ddffff 734 128 / 64 5bc0000-5bdffff 2de0000-2deffff 735 128 / 64 5be0000-5bfffff 2df0000-2dfffff 736 128 / 64 5c00000-5c1ffff 2e00000-2e0ffff 737 128 / 64 5c20000-5c3ffff 2e10000-2e1ffff 738 128 / 64 5c40000-5c5ffff 2e20000-2e2ffff 739 128 / 64 5c60000-5c7ffff 2e30000-2e3ffff 740 128 / 64 5c80000-5c9ffff 2e40000-2e4ffff 741 128 / 64 5ca0000-5cbffff 2e50000-2e5ffff 742 128 / 64 5cc0000-5cdffff 2e60000-2e6ffff 743 128 / 64 5ce0000-5cfffff 2e70000-2e7ffff 744 128 / 64 5d00000-5d1ffff 2e80000-2e8ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 103 745 128 / 64 5d20000-5d3ffff 2e90000-2e9ffff 746 128 / 64 5d40000-5d5ffff 2ea0000-2eaffff 747 128 / 64 5d60000-5d7ffff 2eb0000-2ebffff 748 128 / 64 5d80000-5d9ffff 2ec0000-2ecffff 749 128 / 64 5da0000-5dbffff 2ed0000-2edffff 750 128 / 64 5dc0000-5ddffff 2ee0000-2eeffff 751 128 / 64 5de0000-5dfffff 2ef0000-2efffff 752 128 / 64 5e00000-5e1ffff 2f00000-2f0ffff 753 128 / 64 5e20000-5e3ffff 2f10000-2f1ffff 754 128 / 64 5e40000-5e5ffff 2f20000-2f2ffff 755 128 / 64 5e60000-5e7ffff 2f30000-2f3ffff 756 128 / 64 5e80000-5e9ffff 2f40000-2f4ffff 757 128 / 64 5ea0000-5ebffff 2f50000-2f5ffff 758 128 / 64 5ec0000-5edffff 2f60000-2f6ffff 759 128 / 64 5ee0000-5efffff 2f70000-2f7ffff 760 128 / 64 5f00000-5f1ffff 2f80000-2f8ffff 761 128 / 64 5f20000-5f3ffff 2f90000-2f9ffff 762 128 / 64 5f40000-5f5ffff 22fa00002faffff 763 128 / 64 5f60000-5f7ffff 2fb0000-2fbffff 764 128 / 64 5f80000-5f9ffff 2fc0000-2fcffff 765 128 / 64 5fa0000-5fbffff 2fd0000-2fdffff 766 128 / 64 5fc0000-5fdffff 2fe0000-2feffff 767 128 / 64 5fe0000-5f fffff 2ff0000-2ffffff 768 128 / 64 6000000-601ffff 3000000-300ffff 769 128 / 64 6020000-603ffff 3010000-301ffff 770 128 / 64 6040000-605ffff 3020000-302ffff 771 128 / 64 6060000-607ffff 3030000-303ffff 772 128 / 64 6080000-609ffff 3040000-304ffff 773 128 / 64 60a0000-60bffff 3050000-305ffff 774 128 / 64 60c0000-60dffff 3060000-306ffff 775 128 / 64 60e0000- 60fffff 3070000-307ffff 776 128 / 64 6100000-611ffff 3080000-308ffff 777 128 / 64 6120000-613ffff 3090000-309ffff 778 128 / 64 6140000-615ffff 30a0000-30affff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 104 208045-11 779 128 / 64 6160000-617ffff 30b0000-30bffff 780 128 / 64 6180000-619ffff 30c0000-30cffff 781 128 / 64 61a0000-61bffff 30d0000-30dffff 782 128 / 64 61c0000-61dffff 30e0000-30effff 783 128 / 64 61e0000-61fffff 30f0000-30fffff 784 128 / 64 6200000-621ffff 3100000-310ffff 785 128 / 64 6220000-623ffff 3110000-311ffff 786 128 / 64 6240000-625ffff 3120000-312ffff 787 128 / 64 6260000-627ffff 3130000-313ffff 788 128 / 64 6280000-629ffff 3140000-314ffff 789 128 / 64 62a0000-62bffff 3150000-315ffff 790 128 / 64 62c0000-62dffff 3160000-316ffff 791 128 / 64 62e0000- 62fffff 3170000-317ffff 792 128 / 64 6300000-631ffff 3180000-318ffff 793 128 / 64 6320000-633ffff 3190000-319ffff 794 128 / 64 6340000-635ffff 31a0000-31affff 795 128 / 64 6360000-637ffff 31b0000-31bffff 796 128 / 64 6380000-639ffff 31c0000-31cffff 797 128 / 64 63a0000-63bffff 31d0000-31dffff 798 128 / 64 63c0000-63dffff 31e0000-31effff 799 128 / 64 63e0000-63fffff 31f0000-31fffff 800 128 / 64 6400000-641ffff 3200000-320ffff 801 128 / 64 6420000-643ffff 3210000-321ffff 802 128 / 64 6440000-645ffff 3220000-322ffff 803 128 / 64 6460000-647ffff 3230000-323ffff 804 128 / 64 6480000-649ffff 3240000-324ffff 805 128 / 64 64a0000-64bffff 3250000-325ffff 806 128 / 64 64c0000-64dffff 3260000-326ffff 807 128 / 64 64e0000- 64fffff 3270000-327ffff 808 128 / 64 6500000-651ffff 3280000-328ffff 809 128 / 64 6520000-653ffff 3290000-329ffff 810 128 / 64 6540000-655ffff 32a0000-32affff 811 128 / 64 6560000-657ffff 32b0000-32bffff 812 128 / 64 6580000-659ffff 32c0000-32cffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 105 813 128 / 64 65a0000-65bffff 32d0000-32dffff 814 128 / 64 65c0000-65dffff 32e0000-32effff 815 128 / 64 65e0000-65fffff 32f0000-32fffff 816 128 / 64 6600000-661ffff 3300000-330ffff 817 128 / 64 6620000-663ffff 3310000-331ffff 818 128 / 64 6640000-665ffff 3320000-332ffff 819 128 / 64 6660000-667ffff 3330000-333ffff 820 128 / 64 6680000-669ffff 3340000-334ffff 821 128 / 64 66a0000-66bffff 3350000-335ffff 822 128 / 64 66c0000-66dffff 3360000-336ffff 823 128 / 64 66e0000- 66fffff 3370000-337ffff 824 128 / 64 6700000-671ffff 3380000-338ffff 825 128 / 64 6720000-673ffff 3390000-339ffff 826 128 / 64 6740000-675ffff 33a0000-33affff 827 128 / 64 6760000-677ffff 33b0000-33bffff 828 128 / 64 6780000-679ffff 33c0000-33cffff 829 128 / 64 67a0000-67bffff 33d0000-33dffff 830 128 / 64 67c0000-67dffff 33e0000-33effff 831 128 / 64 67e0000-67fffff 33f0000-33fffff 832 128 / 64 6800000-681ffff 3400000-340ffff 833 128 / 64 6820000-683ffff 3410000-341ffff 834 128 / 64 6840000-685ffff 3420000-342ffff 835 128 / 64 6860000-687ffff 3430000-343ffff 836 128 / 64 6880000-689ffff 3440000-344ffff 837 128 / 64 68a0000-68bffff 3450000-345ffff 838 128 / 64 68c0000-68dffff 3460000-346ffff 839 128 / 64 68e0000- 68fffff 3470000-347ffff 840 128 / 64 6900000-691ffff 3480000-348ffff 841 128 / 64 6920000-693ffff 3490000-349ffff 842 128 / 64 6940000-695ffff 34a0000-34affff 843 128 / 64 6960000-697ffff 34b0000-34bffff 844 128 / 64 6980000-699ffff 34c0000-34cffff 845 128 / 64 69a0000-69bffff 34d0000-34dffff 846 128 / 64 69c0000-69dffff 34e0000-34effff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 106 208045-11 847 128 / 64 69e0000-69fffff 34f0000-34fffff 848 128 / 64 6a00000-6a1ffff 3500000-350ffff 849 128 / 64 6a20000-6a3ffff 3510000-351ffff 850 128 / 64 6a40000-6a5ffff 3520000-352ffff 851 128 / 64 6a60000-6a7ffff 3530000-353ffff 852 128 / 64 6a80000-6a9ffff 3540000-354ffff 853 128 / 64 6aa0000-6abffff 3550000-355ffff 854 128 / 64 6ac0000-6adffff 3560000-356ffff 855 128 / 64 6ae0000-6afffff 3570000-357ffff 856 128 / 64 6b00000-6b1ffff 3580000-358ffff 857 128 / 64 6b20000-6b3ffff 3590000-359ffff 858 128 / 64 6b40000-6b5ffff 35a0000-35affff 859 128 / 64 6b60000-6b7ffff 35b0000-35bffff 860 128 / 64 6b80000-6b9ffff 35c0000-35cffff 861 128 / 64 6ba0000-6bbffff 35d0000-35dffff 862 128 / 64 6bc0000-6bdffff 35e0000-35effff 863 128 / 64 6be0000-6bfffff 35f0000-35fffff 864 128 / 64 6c00000-6c1ffff 3600000-360ffff 865 128 / 64 6c20000-6c3ffff 3610000-361ffff 866 128 / 64 6c40000-6c5ffff 3620000-362ffff 867 128 / 64 6c60000-6c7ffff 3630000-363ffff 868 128 / 64 6c80000-6c9ffff 3640000-364ffff 869 128 / 64 6ca0000-6cbffff 3650000-365ffff 870 128 / 64 6cc0000-6cdffff 3660000-366ffff 871 128 / 64 6ce0000-6cfffff 3670000-367ffff 872 128 / 64 6d00000-6d1ffff 3680000-368ffff 873 128 / 64 6d20000-6d3ffff 3690000-369ffff 874 128 / 64 6d40000-6d5ffff 36a0000-36affff 875 128 / 64 6d60000-6d7ffff 36b0000-36bffff 876 128 / 64 6d80000-6d9ffff 36c0000-36cffff 877 128 / 64 6da0000-6dbffff 36d0000-36dffff 878 128 / 64 6dc0000-6ddffff 36e0000-36effff 879 128 / 64 6de0000-6dfffff 36f0000-36fffff 880 128 / 64 6e00000-6e1ffff 3700000-370ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 107 881 128 / 64 6e20000-6e3ffff 3710000-371ffff 882 128 / 64 6e40000-6e5ffff 3720000-372ffff 883 128 / 64 6e60000-6e7ffff 3730000-373ffff 884 128 / 64 6e80000-6e9ffff 3740000-374ffff 885 128 / 64 6ea0000-6ebffff 3750000-375ffff 886 128 / 64 6ec0000-6edffff 3760000-376ffff 887 128 / 64 6ee0000-6efffff 3770000-377ffff 888 128 / 64 6f00000-6f1ffff 3780000-378ffff 889 128 / 64 6f20000-6f3ffff 3790000-379ffff 890 128 / 64 6f40000-6f5ffff 37a0000-37affff 891 128 / 64 6f60000-6f7ffff 37b0000-37bffff 892 128 / 64 6f80000-6f9ffff 37c0000-37cffff 893 128 / 64 6fa0000-6fbffff 37d0000-37dffff 894 128 / 64 6fc0000-6fdffff 37e0000-37effff 895 128 / 64 6fe0000-6f fffff 37f0000-37fffff 896 128 / 64 7000000-701ffff 3800000-380ffff 897 128 / 64 7020000-703ffff 3810000-381ffff 898 128 / 64 7040000-705ffff 3820000-382ffff 899 128 / 64 7060000-707ffff 3830000-383ffff 900 128 / 64 7080000-709ffff 3840000-384ffff 901 128 / 64 70a0000-70bffff 3850000-385ffff 902 128 / 64 70c0000-70dffff 3860000-386ffff 903 128 / 64 70e0000- 70fffff 3870000-387ffff 904 128 / 64 7100000-711ffff 3880000-388ffff 905 128 / 64 7120000-713ffff 3890000-389ffff 906 128 / 64 7140000-715ffff 38a0000-38affff 907 128 / 64 7160000-717ffff 38b0000-38bffff 908 128 / 64 7180000-719ffff 38c0000-38cffff 909 128 / 64 71a0000-71bffff 38d0000-38dffff 910 128 / 64 71c0000-71dffff 38e0000-38effff 911 128 / 64 71e0000-71fffff 38f0000-38fffff 912 128 / 64 7200000-721ffff 3900000-390ffff 913 128 / 64 7220000-723ffff 3910000-391ffff 914 128 / 64 7240000-725ffff 3920000-392ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 108 208045-11 915 128 / 64 7260000-727ffff 3930000-393ffff 916 128 / 64 7280000-729ffff 3940000-394ffff 917 128 / 64 72a0000-72bffff 3950000-395ffff 918 128 / 64 72c0000-72dffff 3960000-396ffff 919 128 / 64 72e0000- 72fffff 3970000-397ffff 920 128 / 64 7300000-731ffff 3980000-398ffff 921 128 / 64 7320000-733ffff 3990000-399ffff 922 128 / 64 7340000-735ffff 39a0000-39affff 923 128 / 64 7360000-737ffff 39b0000-39bffff 924 128 / 64 7380000-739ffff 39c0000-39cffff 925 128 / 64 73a0000-73bffff 39d0000-39dffff 926 128 / 64 73c0000-73dffff 39e0000-39effff 927 128 / 64 73e0000-73fffff 39f0000-39fffff 928 128 / 64 7400000-741ffff 3a00000-3a0ffff 929 128 / 64 7420000-743ffff 3a10000-3a1ffff 930 128 / 64 7440000-745ffff 3a20000-3a2ffff 931 128 / 64 7460000-747ffff 3a30000-3a3ffff 932 128 / 64 7480000-749ffff 3a40000-3a4ffff 933 128 / 64 74a0000-74bffff 3a50000-3a5ffff 934 128 / 64 74c0000-74dffff 3a60000-3a6ffff 935 128 / 64 74e0000-74fffff 3a70000-3a7ffff 936 128 / 64 7500000-751ffff 3a80000-3a8ffff 937 128 / 64 7520000-753ffff 3a90000-3a9ffff 938 128 / 64 7540000-755ffff 3aa0000-3aaffff 939 128 / 64 7560000-757ffff 3ab0000-3abffff 940 128 / 64 7580000-759ffff 3ac0000-3acffff 941 128 / 64 75a0000-75bffff 3ad0000-3adffff 942 128 / 64 75c0000-75dffff 3ae0000-3aeffff 943 128 / 64 75e0000-75fffff 3af0000-3afffff 944 128 / 64 7600000-761ffff 3b00000-3b0ffff 945 128 / 64 7620000-763ffff 3b10000-3b1ffff 946 128 / 64 7640000-765ffff 3b20000-3b2ffff 947 128 / 64 7660000-767ffff 3b30000-3b3ffff 948 128 / 64 7680000-769ffff 3b40000-3b4ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 109 949 128 / 64 76a0000-76bffff 3b50000-3b5ffff 950 128 / 64 76c0000-76dffff 3b60000-3b6ffff 951 128 / 64 76e0000-76fffff 3b70000-3b7ffff 952 128 / 64 7700000-771ffff 3b80000-3b8ffff 953 128 / 64 7720000-773ffff 3b90000-3b9ffff 954 128 / 64 7740000-775ffff 3ba0000-3baffff 955 128 / 64 7760000-777ffff 3bb0000-3bbffff 956 128 / 64 7780000-779ffff 3bc0000-3bcffff 957 128 / 64 77a0000-77bffff 3bd0000-3bdffff 958 128 / 64 77c0000-77dffff 3be0000-3beffff 959 128 / 64 77e0000-77fffff 3bf0000-3bfffff 960 128 / 64 7800000-781ffff 3c00000-3c0ffff 961 128 / 64 7820000-783ffff 3c10000-3c1ffff 962 128 / 64 7840000-785ffff 3c20000-3c2ffff 963 128 / 64 7860000-787ffff 3c30000-3c3ffff 964 128 / 64 7880000-789ffff 3c40000-3c4ffff 965 128 / 64 78a0000-78bffff 3c50000-3c5ffff 966 128 / 64 78c0000-78dffff 3c60000-3c6ffff 967 128 / 64 78e0000-78fffff 3c70000-3c7ffff 968 128 / 64 7900000-791ffff 3c80000-3c8ffff 969 128 / 64 7920000-793ffff 3c90000-3c9ffff 970 128 / 64 7940000-795ffff 3ca0000-3caffff 971 128 / 64 7960000-797ffff 3cb0000-3cbffff 972 128 / 64 7980000-799ffff 3cc0000-3ccffff 973 128 / 64 79a0000-79bffff 3cd0000-3cdffff 974 128 / 64 79c0000-79dffff 3ce0000-3ceffff 975 128 / 64 79e0000-79fffff 3cf0000-3cfffff 976 128 / 64 7a00000-7a1ffff 3d00000-3d0ffff 977 128 / 64 7a20000-7a3ffff 3d10000-3d1ffff 978 128 / 64 7a40000-7a5ffff 3d20000-3d2ffff 979 128 / 64 7a60000-7a7ffff 3d30000-3d3ffff 980 128 / 64 7a80000-7a9ffff 3d40000-3d4ffff 981 128 / 64 7aa0000-7abffff 3d50000-3d5ffff 982 128 / 64 7ac0000-7adffff 3d60000-3d6ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ memory address table numonyx? axcell? m29ew 110 208045-11 983 128 / 64 7ae0000-7afffff 3d70000-3d7ffff 984 128 / 64 7b00000-7b1ffff 3d80000-3d8ffff 985 128 / 64 7b20000-7b3ffff 3d90000-3d9ffff 986 128 / 64 7b40000-7b5ffff 3da0000-3daffff 987 128 / 64 7b60000-7b7ffff 3db0000-3dbffff 988 128 / 64 7b80000-7b9ffff 3dc0000-3dcffff 989 128 / 64 7ba0000-7bbffff 3dd0000-3ddffff 990 128 / 64 7bc0000-7bdffff 3de0000-3deffff 991 128 / 64 7be0000-7bfffff 3df0000-3dfffff 992 128 / 64 7c00000-7c1ffff 3e00000-3e0ffff 993 128 / 64 7c20000-7c3ffff 3e10000-3e1ffff 994 128 / 64 7c40000-7c5ffff 3e20000-3e2ffff 995 128 / 64 7c60000-7c7ffff 3e30000-3e3ffff 996 128 / 64 7c80000-7c9ffff 3e40000-3e4ffff 997 128 / 64 7ca0000-7cbffff 3e50000-3e5ffff 998 128 / 64 7cc0000-7cdffff 3e60000-3e6ffff 999 128 / 64 7ce0000-7cfffff 3e70000-3e7ffff 1000 128 / 64 7d00000-7d1ffff 3e80000-3e8ffff 1001 128 / 64 7d20000-7d3ffff 3e90000-3e9ffff 1002 128 / 64 7d40000-7d5ffff 3ea0000-3eaffff 1003 128 / 64 7d60000-7d7ffff 3eb0000-3ebffff 1004 128 / 64 7d80000-7d9ffff 3ec0000-3ecffff 1005 128 / 64 7da0000-7dbffff 3ed0000-3edffff 1006 128 / 64 7dc0000-7ddffff 3ee0000-3eeffff 1007 128 / 64 7de0000-7dfffff 3ef0000-3efffff 1008 128 / 64 7e00000-7e1ffff 3f00000-3f0ffff 1009 128 / 64 7e20000-7e3ffff 3f10000-3f1ffff 1010 128 / 64 7e40000-7e5ffff 3f20000-3f2ffff 1011 128 / 64 7e60000-7e7ffff 3f30000-3f3ffff 1012 128 / 64 7e80000-7e9ffff 3f40000-3f4ffff 1013 128 / 64 7ea0000-7ebffff 3f50000-3f5ffff 1014 128 / 64 7ec0000-7edffff 3f60000-3f6ffff 1015 128 / 64 7ee0000-7efffff 3f70000-3f7ffff 1016 128 / 64 7f00000-7f1ffff 3f80000-3f8ffff table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew memory address table 208045-11 111 1017 128 / 64 7f20000-7f3ffff 3f90000-3f9ffff 1018 128 / 64 7f40000-7f5ffff 3fa0000-3faffff 1019 128 / 64 7f60000-7f7ffff 3fb0000-3fbffff 1020 128 / 64 7f80000-7f9ffff 3fc0000-3fcffff 1021 128 / 64 7fa0000-7fbffff 3fd0000-3fdffff 1022 128 / 64 7fc0000-7fdffff 3fe0000-3feffff 1023 128 / 64 7fe0000-7f fffff 3ff0000-3ffffff 1. the 256-mbit device consists of 256 blocks, from block 0 to block 255. 2. the 512-mbit device consists of 512 blocks, from block 0 to block 511. 3. the 1-gbit device consists of 1 024 blocks, from block 0 to block 1023. 4. the 2-gbit device is a 1-gb it/1-gbit stack; there?re in total 2048 blocks, from block 0 to blo ck 2047, including upper die an d bottom die. table 33. block address table for descrete device (up to 1-gbit) (1)(2)(3)(4) block number block size (kbytes / kwords) x8 address (hex) x16 address (hex) http://www..net/ datasheet pdf - http://www..net/ common flash interface (cfi) numonyx? axcell? m29ew 112 208045-11 appendix b common flash interface (cfi) the common flash interface is a jedec approved, standardized data structure that can be read from the flash memory device. it allows a system software to query the device to determine various electrical and timing parameters, density information and functions supported by the memory. the system can interface easily with the device, enabling the software to upgrade itself when necessary. when the read cfi query command is issued, the memory enters read cfi query mode and read operations output the cfi data. ta b l e 3 4 , ta bl e 3 5 , ta b l e 3 6 , ta bl e 3 7 and ta bl e 3 8 and show the addresses (a-1, a0-a7) used to retrieve the data. table 34. query structure overview (1) 1. query data are always presented on the lowest order data outputs. address sub-section name description x16 x8 10h 20h cfi query identification string comm and set id and algorithm data offset 1bh 36h system interface information d evice timing & voltage information 27h 4eh device geometry definition flash device layout 40h 80h primary algorithm-specific extended query table additional information specific to the primary algorithm (optional) table 35. cfi query identification string (1) 1. query data are always presented on the lowest or der data outputs (dq7-dq0) only. dq8-dq15 are ?0?. address data description value x16 x8 10h 20h 0051h ?q? 11h 22h 0052h query unique ascii string ?qry? ?r? 12h 24h 0059h ?y? 13h 26h 0002h primary algorithm command set and control interface id code 16 bit id code defining a specific algorithm amd compatible 14h 28h 0000h 15h 2ah 0040h address for primary algorithm extended query table (see ta b l e 3 8 ) p = 40h 16h 2ch 0000h 17h 2eh 0000h alternate vendor command set and control interface id code second vendor - specified algorithm supported na 18h 30h 0000h 19h 32h 0000h address for alternate algorithm extended query table na 1ah 34h 0000h http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew common flash interface (cfi) 208045-11 113 table 36. cfi query system interface information (1) address data description value x16 x8 1bh 36h 0027h v cc logic supply minimum program/erase voltage bit 7 to 4bcd value in volts bit 3 to 0bcd value in 100 mv 2.7 v 1ch 38h 0036h v cc logic supply maximum program/erase voltage bit 7 to 4bcd value in volts bit 3 to 0bcd value in 100 mv 3.6 v 1dh 3ah 00b5h v pph [programming] supply minimum program/erase voltage bit 7 to 4hex value in volts bit 3 to 0bcd value in 100 mv 11.5 v 1eh 3ch 00c5h v pph [programming] supply maximum program/erase voltage bit 7 to 4hex value in volts bit 3 to 0bcd value in 10 mv 12.5 v 1fh 3eh 0009h typical time-out for single byte/word program = 2 n s 512 s 20h 40h 000ah typical time-out for maximum size buffer program = 2 n s 1024 s 21h 42h 000ah typical time-out for individual block erase = 2 n ms 1 s 22h 44h 0012h / 0013h / 0014h / 0015h typical time-out for full chip erase = 2 n ms 256-mbit 262 s 512-mbit 524 s 1-gbit 1048 s 2-gbit 2097 s 23h 46h 0001h maximum time-out for byte/word program = 2 n times typical time-out 1024 s 24h 48h 0002h maximum time-out for buffer program = 2 n times typical time-out 4096 s 25h 4ah 0002h maximum time-out per individual block erase = 2 n times typical time-out 4s 26h 4ch 0002h maximum time-out for chip erase = 2 n times typical time-out 256-mbit 1048 s 512-mbit 2096 s 1-gbit 4194 s 2-gbit 8388 s 1. the values given in the above table are valid for both packages. http://www..net/ datasheet pdf - http://www..net/ common flash interface (cfi) numonyx? axcell? m29ew 114 208045-11 table 37. device geometry definition address data description value x16 x8 27h 4eh 0019h / 001ah / 001bh/001ch device size = 2 n in number of bytes 32 mbytes 64 mbytes 128 mbytes 256 mbytes 28h 29h 50h 52h 0002h 0000h flash device interface code description x8, x16 async. 2ah 2bh 54h 56h 000ah 0000h maximum number of bytes in multiple-byte program or page= 2 n 1024 (1) 2ch 58h 0001h number of erase block regions. it specifies the number of regions containing contiguous erase blocks of the same size. 1 2dh 2eh 5ah 5ch 00ffh / 00ffh / 00ffh / 00ffh 0000h / 0001h / 0003h / 0007h erase block region 1 information number of erase blocks of identical size = 00ffh + 1 / 01ffh +1 / 03ffh + 1 256 512 1024 2048 2fh 30h 5eh 60h 0000h 0002h erase block region 1 information block size in region 1 = 0200h * 256 byte 128 kbytes 31h 32h 33h 34h 62h 64h 66h 68h 0000h 0000h 0000h 0000h erase block region 2 information 0 35h 36h 37h 38h 6ah 6ch 6eh 70h 0000h 0000h 0000h 0000h erase block region 3 information 0 39h 3ah 3bh 3ch 72h 74h 76h 78h 0000h 0000h 0000h 0000h erase block region 4 information 0 1. for x16/x8 mode, the maximum buffer size is 1024 bytes/256 bytes respectively. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew common flash interface (cfi) 208045-11 115 table 38. primary algorithm-specific extended query table (1) address data description value x16 x8 40h 80h 0050h primary algorithm extended query table unique ascii string ?pri? ?p? 41h 82h 0052h ?r? 42h 84h 0049h ?i? 43h 86h 0031h major version number, ascii ?1? 44h 88h 0033h minor version number, ascii ?3? 45h 8ah 0018h address sensitive unlock (bits 1 to 0) 00 = required, 01= not required silicon revision number (bits 7 to 2) required 46h 8ch 0002h erase suspend 00 = not supported, 01 = read only, 02 = read and write 2 47h 8eh 0001h block protection 00 = not supported, x = number of blocks per group 1 48h 90h 0000h temporary block unprotect 00 = not supported, 01 = supported not supported 49h 92h 0008h block protect / unprotect 08 = m29ewh/m29ewl 8 4ah 94h 0000h simultaneous operations: not supported na 4bh 96h 0000h burst mode, 00 = not supported, 01 = supported not supported 4ch 98h 0003h page mode, 00 = not supported, 01 = 8-word page 02 = 8-word page, 03 = 16-word page 16-word page 4dh 9ah 00b5h v pph supply minimum program/erase voltage bit 7 to 4 hex value in volts bit 3 to 0 bcd value in 100 mv 11.5 v 4eh 9ch 00c5h v pph supply maximum program/erase voltage bit 7 to 4 hex value in volts bit 3 to 0 bcd value in 100 mv 12.5 v 4fh 9eh 00xxh top/bottom boot block flag xx = 04h: uniform device, hw protection for lowest block xx = 05h: uniform device, hw protection for highest block uniform + v pp /wp# protecting highest or lowest block 50h a0h 0001h program suspend, 00 = not supported, 01 = supported supported 1. the values given in the above table are valid for both packages. http://www..net/ datasheet pdf - http://www..net/ extended memory block numonyx? axcell? m29ew 116 208045-11 appendix c extended memory block the m29ew has an extra block, the extended memory block, that can be accessed using a dedicated command. this extended memory block is 128words in x16 mode and 256bytes in x8 mode. it is used as a security block (to provide a permanent security identification number) or to store additional information. the device can be shipped either with the extended memory block pre-locked by numonyx, or unlocked. if the extended memory block is not pre-locked by numonyx, it can be customer-lockable. its status is indicated by bit dq7 of extended memory block verify indicator. this bit is permanently set to either ?1? or ?0? at the numonyx factory and cannot be changed. when set to ?1?, it indicates that the device is pre- locked by numonyx and the extended memory block is protected. when set to ?0?, it indicates that the device is customer-lockable. bit dq7 being permanently locked to either ?1? or ?0? is another security feature which ensures that a customer-lockable device cannot be used instead of a numonyx pre-locked one. bit dq7 is the most significant bit in the extended memory block verify indicator. it can be read in auto select mode using either the programmer (see ta b l e 7 and ta bl e 8 ) or the in- system method (see ta b l e 9 and ta b l e 1 0 ). the extended memory block can only be accessed when the device is in extended memory block mode. for details of how the extended memory block mode is entered and exited, refer to the section 6.3.1: enter extende d memory block command and section 6.3.2: exit extended memory block command , and to ta bl e 1 3 and ta b l e 9 . c.1 numonyx pre-locked extended memory block if devices of which the extended memory block is pre-locked upon customer request, the 128bits security identification number is written to the extended memory block address space (see table 39: extended memory block address and data ) in numonyx factory. the contents in the extended memory block cannot be changed any more. http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew extended memory block 208045-11 117 c.2 customer-lockable extended memory block a device where the extended memory block is customer-lockable is delivered with the dq7 bit set to ?0? and the extended memory block unprotected. it is up to the customer to program and protect the extended memory block but care must be taken because the protection of the extended memory block is not reversible. if the device has not been shipped with the extended memory block pre-protected, the block can be protected by setting the extended memory block protection bit, dq0, to ?0?. however, this bit can only be programmed once; and once it is protected the extended memory block cannot be unprotected. once the extended memory block is programmed, the exit extended memory block command must be issued to exit the extended memory block mode and return the device to read mode. table 39. extended memory block address and data address (1) data x8 x16 numonyx pre-locked customer-lockable 000000h-00000fh 000000h-000007h secure identification number determined by customers (default) secure identification number 000010h-0000ffh 000008h-00007fh protected and unavailable determined by customers 1. http://www..net/ datasheet pdf - http://www..net/ revision history numonyx? axcell? m29ew 118 208045-11 appendix d revision history table 40. document revision history date version changes may 2008 01 initial release oct 2008 02 update t avav values in ta b l e 2 4 and ta bl e 2 5 move buffer program flow chart to chapter 6.2.1, as figure 8 minor wording changes dec 2008 03 apply axcell tm as m29ew?s branding name change the names of timing parameters in ta b l e 2 0 , ta b l e 2 6 and ta b l e 2 7 modify many waveforms to align the signal names some wording changes spec change of t ehel2 from 20ns to 30ns, in ta b l e 2 7 remove ?numonyx confidential? remove conventions section and set revision history as appendix d update physical dimension information in ta b l e 2 9 add document number add 1-gbit and 512-mbit information into the data sheet correct some typo error mar 2009 04 correct the buffer write cycle numbers and wording correction in ta b l e 1 1 and ta bl e 1 2 fix a text corruption in figure 8 remove invalid ship options in chapter 5.1 add figure 7 to explain the buffer programming add buffer write misalignment description to better explain buffer programming usage in chapter 6.2.1 move the disclaimer to the end of the data sheet add 10kohm pull-up resistor description for ry/by# pin update fortified bga physical dimension of ball size ta bl e 3 0 apr 2009 05 remove notes about enhanced buffer programming in chapter 6.2.2 change v pph spec in ta bl e 1 8 and ta bl e 1 9 change the address for vpb read in ta bl e 1 3 and ta bl e 1 4 correct the dq2 toggling states in ta b l e 1 7 jun 2009 06 add technology information in cover page and chapter 1 add rohs and halogen free information in cover page add block address information in chapter appendix a move programming and erase perf ormance as separate chapter in chapter 10 add leaded, rohs, halogen free information in chapter 12 oct 2009 07 add 2-gbit (1-gbit/1-gbit ) stack device related information http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew revision history 208045-11 119 feb 2010 08 revised part numbers in the table 32.: valid combinations of m29ew part numbers update programming performance specifications and suspend latency specifications in table 28: programming and erase performance update cfi information of program max timeout in table 36: cfi query system interface information add erase to suspend specification in table 28: programming and erase performance add note for tdvwh in table 24: write ac characteristics, write enable controlled add note for tdveh in table 25: write ac characteristics, chip enable controlled apr 2010 09 update jedec compliance in cover page correct the buffer programming boundary limitation in section 6.2.1: write to buffer program command update the specification of t plrh (t ready ) in table 26: reset ac characteristics update the description of v pp /wp# pin in chapter 2.8: v pp /write protect (v pp/ wp#) add byte# transition waveform as figure 19: byte# transition ac waveform may 2010 10 update the random read ac waveforms about byte# pin in section 9: dc and ac parameters put a link for product part numbers in section 12: ordering information apr 2011 11 add a block diagram figure 2: 2-gbit (1-gbit/1-gbit stack) configurations to emphasize 2g part is 1g/1g stack, not discrete one remove the invalid automatic standby mode from front page and section 3: bus operations on page 17 add t whwh1 specification at table 24: write ac characteristics, write enable controlled and table 25: write ac characteristics, chip enable controlled at cfi table offset 2ah/2bh (x16), add a note for x8 mode to emphasize its maximum buffer size is 256 bytes for read id and read protection status, align with device about higher address pins input status at ta b l e 5 , ta b l e 6 , ta b l e 7 and ta b l e 8 add jedec standard lead width for tsop56 package at ta bl e 2 9 : t s o p 5 6 ? 56 lead thin small-outline package, 14 x 20 mm, package mechanical data on page 78 correct the glitch filter from 5ns to 3ns remove the invalid statement about applyi ng vid to a9 to enter auto select mode at section 7.1.3: extended memory block protection bit (dq0) add blank check related information align with device about dq2 toggle st atus when erase/blank check error happens at table 17: status register bits date version changes http://www..net/ datasheet pdf - http://www..net/ numonyx? axcell? m29ew 120 please read carefully: information in this document is provided in connection with numonyx ? products. no license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. except as provided in numonyx's terms and conditions of sale for such products, numonyx assumes no liability whatsoever, and numonyx disclaims any express or implied warranty, relating to sale and/or use of numonyx products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. numonyx products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in n uclear facility applications. numonyx may make changes to specifications and product descriptions at any time, without notice. numonyx, b.v. may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights th at relate to the presented subject matter. the furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. designers must not rely on the absence or characteristics of any features or instructions marked ?reserved? or ?undefined.? num onyx reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. contact your local numonyx sales office or your distributor to obtain the latest specifications and before placing your product order. copies of documents which have an order number and are referenced in this document, or other numonyx literature may be obtained by visiting numonyx's website at http://www.numonyx.com . numonyx? axcell is a trademark or registered trademark of numonyx or its subsidiaries in the united states and other countries. *other names and brands may be claimed as the property of others. copyright ? 2009, numonyx, b.v., all rights reserved. http://www..net/ datasheet pdf - http://www..net/ |
Price & Availability of JS28F00AM29EWHX
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |